Triple
T25049370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casselman River Bridge State Park |
E627332
|
entity |
| Predicate | currentBridgeUse |
P162984
|
FINISHED |
| Object | pedestrian use |
—
|
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: pedestrian use | Statement: [Casselman River Bridge State Park, currentBridgeUse, pedestrian use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentBridgeUse Context triple: [Casselman River Bridge State Park, currentBridgeUse, pedestrian use]
-
A.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
B.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
C.
hasBridgeAccess
Indicates that an entity is permitted to enter or use a specific bridge or bridge-controlled area.
-
D.
hasBridgeCrossings
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
E.
bridgeStatus
Indicates the current operational condition or availability state of a bridge (e.g., open, closed, restricted).
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f63639a84c81909d700a539b458b42 |
completed | May 2, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 18, 2026, 6:08 a.m.