Triple
T30278581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niagara Falls Bridge Commission |
E770022
|
entity |
| Predicate | hasBridgeTypeOperated |
P178818
|
FINISHED |
| Object | arch bridge |
—
|
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: arch bridge | Statement: [Niagara Falls Bridge Commission, hasBridgeTypeOperated, arch bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeTypeOperated Context triple: [Niagara Falls Bridge Commission, hasBridgeTypeOperated, arch bridge]
-
A.
hasBridgePerformedBy
Indicates that a specific bridge (e.g., a musical or structural segment) is carried out, executed, or performed by a particular agent or performer.
-
B.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
C.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
D.
hasBridgeAccess
Indicates that an entity is permitted to enter or use a specific bridge or bridge-controlled area.
-
E.
hasBuildingTypeOnBridge
Indicates that a specific type of building or structure is located on or constructed upon a bridge.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 29, 2026, 7:45 p.m.