Triple
T29203861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Haneda – Naha |
E740354
|
entity |
| Predicate | sameCountryOriginDestination |
P152159
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tokyo Haneda – Naha, sameCountryOriginDestination, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sameCountryOriginDestination Context triple: [Tokyo Haneda – Naha, sameCountryOriginDestination, true]
-
A.
hasOriginAirport
Indicates that something, typically a flight or journey, departs from or is associated with a specific origin airport.
-
B.
hasOriginAirportCity
Indicates that an entity (such as a flight or trip) departs from or is associated with a specific origin airport located in a given city.
-
C.
voyageOriginCountry
Indicates the country from which a voyage departs or originates.
-
D.
isDomesticRouteIn
chosen
Indicates that a transportation route operates entirely within the boundaries of a specified country or internal region.
-
E.
hasTypicalOriginAirport
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.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c7b4f48190b66f966af570e768 |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:08 p.m.