Triple
T29922794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天草飛行場 |
E759991
|
entity |
| Predicate | 開設目的 |
P32787
|
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.
purposeOfFoundation
chosen
Indicates the reason or intended goal for which an organization, institution, or entity was originally established.
-
B.
aimedToEstablish
Indicates an intention or effort directed toward creating, founding, or setting up something.
-
C.
purposeOfIncorporation
Indicates that an entity was incorporated with the specific goal, function, or intended activity described by another entity or statement.
-
D.
hasEstablishedPurpose
Indicates that an entity has a defined and recognized purpose or intended function already determined.
-
E.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
- 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.