Triple
T5990331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wells Street Bridge |
E133331
|
entity |
| Predicate | basculeType |
P33205
|
FINISHED |
| Object | trunnion bascule |
—
|
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: trunnion bascule | Statement: [Wells Street Bridge, basculeType, trunnion bascule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basculeType Context triple: [Wells Street Bridge, basculeType, trunnion bascule]
-
A.
hasBasculeMechanism
chosen
Indicates that one entity is equipped with or incorporates a bascule (pivoting or counterweighted) mechanism provided by the other entity.
-
B.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
C.
riverCrossingStructure
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
D.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
-
E.
berthType
Indicates the specific kind or category of berth associated with an entity, such as the type of sleeping or docking space provided.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc8ab648190beb1bc141796894e |
completed | March 22, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.