Triple
T25447482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nairobi–London |
E637674
|
entity |
| Predicate | usesIATACityCodeDestination |
P152161
|
FINISHED |
| Object | LON |
—
|
LITERAL FINISHED |
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: LON | Statement: [Nairobi–London, usesIATACityCodeDestination, LON]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIATACityCodeDestination Context triple: [Nairobi–London, usesIATACityCodeDestination, LON]
-
A.
usesIATACityCodeOrigin
Indicates that the origin location in a context (such as a trip, flight, or route) is specified using its IATA city code.
-
B.
usesIATACodeAtOtherEnd
chosen
Indicates that one entity identifies or refers to the other end of a route, connection, or relationship using its IATA airport code.
-
C.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
D.
IATAcode
Indicates the three-letter IATA airport or airline code assigned to the entity.
-
E.
hasIATAFunction
Indicates that an entity has a specific role, status, or function as defined by the International Air Transport Association (IATA).
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 2:02 p.m.