Triple
T35442716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leros–Athens |
E1024393
|
entity |
| Predicate | hasIATAAirportOnRoute |
P2569
|
FINISHED |
| Object | LRS |
—
|
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: LRS | Statement: [Leros–Athens, hasIATAAirportOnRoute, LRS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIATAAirportOnRoute Context triple: [Leros–Athens, hasIATAAirportOnRoute, LRS]
-
A.
hasIATAFunction
Indicates that an entity has a specific role, status, or function as defined by the International Air Transport Association (IATA).
-
B.
hasIATAcode
chosen
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
C.
hasEndpointAirport
Indicates that something, such as a route or flight, has a specific airport as one of its terminal endpoints.
-
D.
hasIATAFlightNumber
Indicates that an entity (typically a flight) is associated with a specific IATA-designated flight number.
-
E.
hasOriginAirport
Indicates that something, typically a flight or journey, departs from or is associated with a specific origin airport.
- 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_69f76df8089481909f0018266ee881b7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7961d2fb08190bf1ee368e152feda |
completed | May 3, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:04 p.m.