Triple
T26789526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oich Bridge |
E670475
|
entity |
| Predicate | isMovableBridge |
P161238
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oich Bridge, isMovableBridge, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMovableBridge Context triple: [Oich Bridge, isMovableBridge, true]
-
A.
hasSwingBridge
Indicates that one entity possesses or includes a swing bridge, i.e., a bridge section that can pivot or rotate to allow passage (typically of water traffic).
-
B.
hasBridgeOrStructure
Indicates that there exists a bridge or similar structural connection between the related entities.
-
C.
hasBuildingTypeOnBridge
Indicates that a specific type of building or structure is located on or constructed upon a bridge.
-
D.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
-
E.
hasRailBridge
Indicates that one location or structure is connected to another by a bridge specifically designed to carry railway tracks or trains.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f619b933dc8190994b3951c1ee89ab |
completed | May 2, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 4:15 a.m.