Triple
T28632981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukuoka–Tokyo Haneda |
E724694
|
entity |
| Predicate | airportAtOneEnd |
P37080
|
FINISHED |
| Object | Fukuoka 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: Fukuoka Airport | Statement: [Fukuoka–Tokyo Haneda, airportAtOneEnd, Fukuoka Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportAtOneEnd Context triple: [Fukuoka–Tokyo Haneda, airportAtOneEnd, Fukuoka Airport]
-
A.
airportStation
Indicates a location functions as an airport facility where air transport operations occur.
-
B.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
C.
airportServesAs
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
-
D.
hasEndpointAirport
chosen
Indicates that something, such as a route or flight, has a specific airport as one of its terminal endpoints.
-
E.
airportLocatedWithin
Indicates that an airport is geographically situated inside the boundaries of a specified area or region.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 4:38 a.m.