Triple
T29922817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天草飛行場 |
E759991
|
entity |
| Predicate | 管轄航空局 |
P77412
|
FINISHED |
| Object | 大阪航空局 |
—
|
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: 大阪航空局 | Statement: [天草飛行場, 管轄航空局, 大阪航空局]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 管轄航空局 Context triple: [天草飛行場, 管轄航空局, 大阪航空局]
-
A.
airlineRegulatoryAuthority
Indicates that one entity serves as the official regulatory authority overseeing and governing the operations of an airline or airlines.
-
B.
aviationAuthority
chosen
Indicates that one entity serves as the official aviation regulatory or oversight body responsible for governing, certifying, or supervising the other entity’s aviation-related activities.
-
C.
isPartOfAviationSystem
Indicates that something functions as a component or subsystem within a broader aviation system or infrastructure.
-
D.
operatesUnderAirOperatorCertificateOf
Indicates that one entity conducts its aviation operations under the authority, terms, and oversight of another entity’s air operator certificate.
-
E.
flightTestAgency
Indicates that an agency is responsible for conducting or overseeing flight tests for an aerospace vehicle or system.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677953ad0819099fa0d8006a65679 |
completed | May 2, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:15 p.m.