Triple
T23949687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chile national transport system |
E603010
|
entity |
| Predicate | mainInternationalAirportCity |
P1813
|
FINISHED |
| Object | Santiago |
—
|
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: Santiago | Statement: [Chile national transport system, mainInternationalAirportCity, Santiago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainInternationalAirportCity Context triple: [Chile national transport system, mainInternationalAirportCity, Santiago]
-
A.
hasInternationalAirport
chosen
Indicates that a place possesses an airport that handles international flights and services cross-border air traffic.
-
B.
isOnlyInternationalAirportOf
Indicates that an airport is the single, unique international airport serving a particular city, region, or country.
-
C.
hubAirportCity
Indicates that a city serves as a primary hub location for an airport or airline.
-
D.
isInternationalAirportCode
Indicates that a given code designates an airport in the standardized international airport coding system (such as IATA or ICAO).
-
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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d03140f08190b4356626628ff56f |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:19 p.m.