Triple
T6035771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaSalle Street Bridge |
E134416
|
entity |
| Predicate | hasLowerDeckFunction |
P68896
|
FINISHED |
| Object | service and utilities |
—
|
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: service and utilities | Statement: [LaSalle Street Bridge, hasLowerDeckFunction, service and utilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerDeckFunction Context triple: [LaSalle Street Bridge, hasLowerDeckFunction, service and utilities]
-
A.
hasLowerFloor
Indicates that one location, structure, or level includes or is directly connected to a floor situated below another floor.
-
B.
hasUndercarriageType
Indicates the specific type or configuration of undercarriage that an object (typically a vehicle or machine) possesses.
-
C.
hasLowerBarLength
Indicates that one entity’s bar length is shorter than the bar length of another entity.
-
D.
hasLowerTier
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
-
E.
hasCargoDoorVariant
Indicates that one entity is a specific cargo-door-equipped version or configuration variant of another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:08 p.m.