Triple
T4282677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Avenue Bridge |
E97189
|
entity |
| Predicate | hasMovableSpanType |
P25282
|
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: [University Avenue Bridge, hasMovableSpanType, trunnion bascule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMovableSpanType Context triple: [University Avenue Bridge, hasMovableSpanType, trunnion bascule]
-
A.
hasMovableSpan
chosen
Indicates that an object or structure includes a span or section that can be moved or repositioned rather than being fixed in place.
-
B.
isSpanning
Indicates that one entity extends across, covers, or bridges the full width, extent, or duration of another entity.
-
C.
hasMovementType
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
D.
hasMainSpanLength
Indicates the relationship specifying the primary or main span’s length associated with an entity.
-
E.
hasSegmentType
Indicates that an entity is associated with, or classified by, a particular type or category of segment within a larger structure or sequence.
- 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_69b3454595848190a0e6bbb6a2bea040 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3503a84548190989a96d1a30d6ef7 |
completed | March 12, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.