Triple
T14764662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seto Ohashi Bridge |
E346961
|
entity |
| Predicate | heightRestrictionRoad |
P115703
|
FINISHED |
| Object | about 4.5 m |
—
|
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: about 4.5 m | Statement: [Seto Ohashi Bridge, heightRestrictionRoad, about 4.5 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightRestrictionRoad Context triple: [Seto Ohashi Bridge, heightRestrictionRoad, about 4.5 m]
-
A.
hasLimitedRoadAccess
Indicates that an entity can only be reached by a small number of roads, restricted routes, or otherwise constrained vehicular access.
-
B.
roadWidth
Indicates the measured breadth or distance across a road, typically from one edge or curb to the opposite edge or curb.
-
C.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
-
D.
hasRoadAbove
Indicates that one road segment is physically located above another, such as on an overpass, bridge, or elevated structure.
-
E.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f3a1608190b1b17624003a0c7f |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.