Triple
T8957749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldiers Field Road |
E213517
|
entity |
| Predicate | hasBridgeUnderpasses |
P85871
|
FINISHED |
| Object | multiple low-clearance bridges |
—
|
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: multiple low-clearance bridges | Statement: [Soldiers Field Road, hasBridgeUnderpasses, multiple low-clearance bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBridgeUnderpasses Context triple: [Soldiers Field Road, hasBridgeUnderpasses, multiple low-clearance bridges]
-
A.
hasBridgeTunnel
Indicates that there exists a bridge or tunnel connection between two locations or structures.
-
B.
hasBridgeOrStructure
Indicates that there exists a bridge or similar structural connection between the related entities.
-
C.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
D.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
-
E.
hasMajorBridge
Indicates that one entity possesses or includes a primary or significant bridge associated with it.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6729ab7c8190a6168f0aa70a5520 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7 p.m.