Triple
T25850118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIRDO |
E651176
|
entity |
| Predicate | operatesDomesticFlightsBetween |
P1658
|
FINISHED |
| Object | Hokkaido and Tokyo |
—
|
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: Hokkaido and Tokyo | Statement: [AIRDO, operatesDomesticFlightsBetween, Hokkaido and Tokyo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesDomesticFlightsBetween Context triple: [AIRDO, operatesDomesticFlightsBetween, Hokkaido and Tokyo]
-
A.
operatesFlightsTo
Indicates that one entity (typically an airline) runs or provides flight services to the location represented by the other entity.
-
B.
hasDomesticFlights
chosen
Indicates that an airline or airport operates flights within the same country, connecting domestic destinations.
-
C.
servesFlightsTo
Indicates that one transportation provider regularly operates flights to a specified destination location.
-
D.
operatesFlightsInRegion
Indicates that an airline or carrier runs or provides flight services within a specified geographic region.
-
E.
operatesFeederFlightsFor
Indicates that one airline or carrier runs connecting or short-haul feeder flights on behalf of, or in support of, another airline’s main services.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 22, 2026, 7:58 a.m.