Triple
T14341059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seto-Chuo Expressway |
E355603
|
entity |
| Predicate | hasBridgeSystem |
P49473
|
FINISHED |
| Object | multiple long-span bridges |
—
|
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: multiple long-span bridges | Statement: [Seto-Chuo Expressway, hasBridgeSystem, multiple long-span bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeSystem Context triple: [Seto-Chuo Expressway, hasBridgeSystem, multiple long-span bridges]
-
A.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
B.
spannedByBridgeSystem
chosen
Indicates that one location or area is connected to another by a system of bridges spanning between them.
-
C.
hasBridgeCrossings
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
D.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
E.
hasMajorBridge
Indicates that one entity possesses or includes a primary or significant bridge associated with it.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e87febc8190a63c668cbd0fd713 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.