Triple
T25715358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London–Sydney |
E644847
|
entity |
| Predicate | typicalStartAirport |
P90677
|
FINISHED |
| Object | London Heathrow Airport |
—
|
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: London Heathrow Airport | Statement: [London–Sydney, typicalStartAirport, London Heathrow Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStartAirport Context triple: [London–Sydney, typicalStartAirport, London Heathrow Airport]
-
A.
typicalOriginAirportIATA
Indicates the usual or primary origin airport for an entity, identified by its IATA airport code.
-
B.
typicalDestinationAirportIATA
Indicates the IATA airport code that is typically the destination in this kind of trip or route.
-
C.
hasTypicalOriginAirport
chosen
Indicates that an entity, such as a flight route or airline service, is commonly or usually associated with a particular origin airport from which it typically departs.
-
D.
originAirportICAO
Indicates the airport, identified by its ICAO code, from which a flight or journey departs.
-
E.
parentAirport
Indicates that one airport serves as the primary or overarching facility from which another, subsidiary or associated airport is derived or managed.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 21, 2026, 9:40 p.m.