Triple
T8833144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amakusa Airfield |
E210194
|
entity |
| Predicate | servesDomesticTrafficOnly |
P1658
|
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: [Amakusa Airfield, servesDomesticTrafficOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesDomesticTrafficOnly Context triple: [Amakusa Airfield, servesDomesticTrafficOnly, true]
-
A.
hasDomesticTerminal
Indicates that a transportation facility, typically an airport, includes a terminal dedicated to domestic (within-country) travel operations.
-
B.
hasDomesticConcourse
Indicates that a transportation facility includes a concourse area designated for domestic (within-country) passengers or services.
-
C.
hasNoInternationalCrossing
Indicates that there is no crossing or connection between the entities that extends across international borders.
-
D.
hasPassengerTrafficFrom
Indicates that an entity receives or handles passenger traffic originating from another entity.
-
E.
hasDomesticFlights
chosen
Indicates that an airline or airport operates flights within the same country, connecting domestic destinations.
- 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_69ca8388549c819095fd94eadefbb007 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60670fa48190b2a873f6498de7f6 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.