Triple
T22582784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLUY |
E544608
|
entity |
| Predicate | airportServedRegion |
P4363
|
FINISHED |
| Object | Potosí Department |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Potosí Department | Statement: [SLUY, airportServedRegion, Potosí Department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportServedRegion Context triple: [SLUY, airportServedRegion, Potosí Department]
-
A.
airportServed
chosen
Indicates that a particular airport provides service to, or is used for air travel to and from, a given location or area.
-
B.
airportServesAs
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
-
C.
associatedAirportServes
Indicates that a given airport provides service to, or is used by, the associated entity (such as a city, region, or facility).
-
D.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
E.
isMajorRegionalAirportFor
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15ff26d6481908cc058f8c4b87e75 |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.