Triple
T28879109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伊良部大橋 |
E732362
|
entity |
| Predicate | 架橋目的 |
P165690
|
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.
関連橋梁
Indicates a relationship in which one bridge is associated with, connected to, or otherwise related to another bridge.
-
B.
bridgeStructure
Indicates a structural relationship where one entity functions as a bridge that spans or connects two separate points or areas.
-
C.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
D.
riverCrossingStructure
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
E.
bridgeLiftUsedFor
Indicates that a bridge is raised or lifted to allow a particular purpose, such as the passage or use of something beneath or through it.
- F. None of above. chosen
Provenance (4 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a4d874c819094de2d585e1f5816 |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 7:41 a.m.