Triple
T30240531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amakusa Airport |
E768899
|
entity |
| Predicate | servesDomestic |
P195389
|
FINISHED |
| Object | Japan |
—
|
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 | Statement: [Amakusa Airport, servesDomestic, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesDomestic Context triple: [Amakusa Airport, servesDomestic, Japan]
-
A.
servedDomesticDestination
chosen
Indicates that a transportation service (such as an airline or train operator) provided service to a destination located within the same country.
-
B.
isDomestic
Indicates that an entity exists or is used primarily within a home or internal context rather than in a foreign or wild environment.
-
C.
hasDomesticServices
Indicates that an entity provides or is associated with services intended for use within a home or domestic setting.
-
D.
hasDomesticOperations
Indicates that an entity conducts business activities or operational functions within its own home country or internal jurisdiction.
-
E.
homeCountryDomesticSystem
Indicates that something is part of, governed by, or operating within the domestic system of its home country.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 29, 2026, 7:38 p.m.