Triple
T3031638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steel Bridge |
E82909
|
entity |
| Predicate | hasVerticalClearanceWhenRaised |
P12201
|
FINISHED |
| Object | about 163 feet |
—
|
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: about 163 feet | Statement: [Steel Bridge, hasVerticalClearanceWhenRaised, about 163 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerticalClearanceWhenRaised Context triple: [Steel Bridge, hasVerticalClearanceWhenRaised, about 163 feet]
-
A.
clearanceBelowWhenRaised
chosen
Indicates that when one object is raised, there is a specified amount of vertical space (clearance) remaining below it relative to another object or reference surface.
-
B.
hasRetractablePitch
Indicates that an entity (typically a stadium or venue) possesses a playing surface or pitch that can be mechanically extended or withdrawn as needed.
-
C.
hasLift
Indicates that one entity is equipped with, contains, or provides access to a lift (elevator).
-
D.
hasLiftType
Indicates the specific type or category of lift associated with an entity.
-
E.
cargoHoldHeight
Indicates the vertical interior dimension or clearance height of a cargo hold space.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aee2fec81908116939a8d773fc4 |
completed | March 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.