Triple
T37589044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Japan |
E935204
|
entity |
| Predicate | hasAirportHub |
P134018
|
FINISHED |
| Object | Narita International 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: Narita International Airport | Statement: [East Japan, hasAirportHub, Narita International Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAirportHub Context triple: [East Japan, hasAirportHub, Narita International Airport]
-
A.
associatedHubAirport
chosen
Indicates that one entity serves as a primary or hub airport functionally linked to the other entity.
-
B.
hasAirportCenter
Indicates that an airport is centrally located within, or serves as the main air transport hub for, a specified area or region.
-
C.
hasMajorCityHub
Indicates that an entity contains or is associated with a primary, high-importance city that functions as a central hub for activity, services, or connectivity.
-
D.
associatedAirportPrimaryHubFor
Indicates that an airport serves as the primary hub for a particular airline or transportation operator.
-
E.
hasMajorAirport
Indicates that a location possesses at least one significant airport that serves as a primary hub for air travel in that area.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.