Triple
T9930184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokunoshima Airport |
E192626
|
entity |
| Predicate | domesticOrInternational |
P89290
|
FINISHED |
| Object | domestic |
—
|
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: domestic | Statement: [Tokunoshima Airport, domesticOrInternational, domestic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domesticOrInternational Context triple: [Tokunoshima Airport, domesticOrInternational, domestic]
-
A.
isInternational
Indicates that something has a connection to, involves, or extends across more than one country.
-
B.
internationalDestinationsInclude
Indicates that a given entity’s set of international destinations contains or covers the specified destination(s).
-
C.
isDomesticAirport
chosen
Indicates that an airport primarily handles flights within the same country, rather than international routes.
-
D.
hasDomesticFlights
Indicates that an airline or airport operates flights within the same country, connecting domestic destinations.
-
E.
hasNoInternationalCrossing
Indicates that there is no crossing or connection between the entities that extends across international borders.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b4196881909a004091a4203c45 |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.