Triple
T28879117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 伊良部大橋 |
E732362
|
entity |
| Predicate | 交通手段への影響 |
P3830
|
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.
transportationImpact
chosen
Indicates how one entity’s transportation-related activities or characteristics affect another entity or the surrounding environment.
-
B.
passesUsedForTransportation
Indicates that the passes are utilized as a means or instrument for transporting people or goods.
-
C.
usedTransportationInfrastructure
Indicates that an entity made use of some form of transportation infrastructure (such as roads, railways, or ports) to enable movement or transit.
-
D.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
-
E.
transportModeImportant
Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
- 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_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. |
Created at: April 28, 2026, 7:41 a.m.