Triple
T23086626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parkway East (Interstate 376) |
E575620
|
entity |
| Predicate | hasTunnelsOrBridges |
P50312
|
FINISHED |
| Object | multiple 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 bridges | Statement: [Parkway East (Interstate 376), hasTunnelsOrBridges, multiple bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTunnelsOrBridges Context triple: [Parkway East (Interstate 376), hasTunnelsOrBridges, multiple bridges]
-
A.
hasBridges
chosen
Indicates that one entity possesses, contains, or is characterized by one or more bridges connecting locations or components.
-
B.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are associated with a given entity.
-
C.
hasTunnelsOnRoad
Indicates that a road includes or passes through one or more tunnels along its route.
-
D.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
E.
hasBridgeTunnel
Indicates that there exists a bridge or tunnel connection between two locations or structures.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da652ac819085919ade6dd7bce4 |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:57 p.m.