Triple
T15278997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kita Bisan-Seto Bridge |
E365219
|
entity |
| Predicate | isEngineeringStructureOf |
P117926
|
FINISHED |
| Object | Seto Ohashi Line |
—
|
NE NERFINISHED |
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: Seto Ohashi Line | Statement: [Kita Bisan-Seto Bridge, isEngineeringStructureOf, Seto Ohashi Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEngineeringStructureOf Context triple: [Kita Bisan-Seto Bridge, isEngineeringStructureOf, Seto Ohashi Line]
-
A.
isEngineeredStructure
Indicates that something is a man-made or artificially constructed structure, typically designed and built through engineering processes.
-
B.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
C.
hasStructuralEngineer
Indicates that an entity is associated with or employs a structural engineer responsible for its structural design, analysis, or integrity.
-
D.
hasEngineeringSignificance
Indicates that something holds notable importance, impact, or relevance within an engineering context or for engineering activities.
-
E.
hasEngineeringBy
Indicates that something is designed, planned, or constructed by a specified engineer or engineering entity.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e504d8c8190ad6c565a31d1a9bd |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:14 a.m.