Triple
T6035770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaSalle Street Bridge |
E134416
|
entity |
| Predicate | hasUpperDeckFunction |
P32506
|
FINISHED |
| Object | vehicular traffic |
—
|
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: vehicular traffic | Statement: [LaSalle Street Bridge, hasUpperDeckFunction, vehicular traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperDeckFunction Context triple: [LaSalle Street Bridge, hasUpperDeckFunction, vehicular traffic]
-
A.
upperDeckUsedFor
chosen
Indicates that the upper deck of an object or structure is utilized for a specified purpose or activity.
-
B.
hasExpansionSetNumber
Indicates that an entity is associated with a specific numbered position or identifier within an expansion set.
-
C.
upperDeckDirection
Indicates the direction or orientation associated with the upper deck relative to a reference point or structure.
-
D.
hasDeckType
Indicates that an entity possesses or is associated with a specific type or category of deck.
-
E.
isThroughDeck
Indicates that one object passes completely through another object or surface, extending from one side to the other.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b4e3ec819089b2d119ea2953fe |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.