Triple
T32602192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okinoerabu Airport |
E833404
|
entity |
| Predicate | hasFlightOperator |
P34771
|
FINISHED |
| Object | Japan Air Commuter |
—
|
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: Japan Air Commuter | Statement: [Okinoerabu Airport, hasFlightOperator, Japan Air Commuter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightOperator Context triple: [Okinoerabu Airport, hasFlightOperator, Japan Air Commuter]
-
A.
airlineOperator
Indicates that one entity operates or manages airline services for another entity or in a specified context.
-
B.
aircraftOperator
Indicates that one entity operates, manages, or is responsible for the use of a particular aircraft.
-
C.
belongsToAirportOperator
chosen
Indicates that an airport or related facility is owned, managed, or operated by a specific airport operating organization.
-
D.
hasPassengerOperator
Indicates that an entity (such as a vehicle or service) is operated by an organization or person responsible for carrying passengers.
-
E.
operatedForAirline
Indicates that an aircraft or flight was operated on behalf of, or under the branding of, a particular airline.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:05 a.m.