Triple
T29307243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ho Chi Minh City–Da Nang |
E743127
|
entity |
| Predicate | hasIATAAirport2 |
P2569
|
FINISHED |
| Object | DAD |
—
|
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: DAD | Statement: [Ho Chi Minh City–Da Nang, hasIATAAirport2, DAD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIATAAirport2 Context triple: [Ho Chi Minh City–Da Nang, hasIATAAirport2, DAD]
-
A.
hasIATAcode
chosen
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
B.
hasIATAFunction
Indicates that an entity has a specific role, status, or function as defined by the International Air Transport Association (IATA).
-
C.
hasIcaoAirport
Indicates that an entity is associated with an airport identified by a specific ICAO (International Civil Aviation Organization) airport code.
-
D.
hasIataAirportCodeContext
Indicates that an entity is associated with a specific IATA airport code within a particular contextual scope or usage.
-
E.
IATAcode
Indicates the three-letter IATA airport or airline code assigned to the entity.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665a6fbb88190bae8ba90855eadda |
completed | May 2, 2026, 8:59 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 1:14 p.m.