Triple
T20555306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Canada Highway near Revelstoke |
E504704
|
entity |
| Predicate | hasSafetyConcerns |
P103393
|
FINISHED |
| Object | winter driving conditions |
—
|
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: winter driving conditions | Statement: [Trans-Canada Highway near Revelstoke, hasSafetyConcerns, winter driving conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyConcerns Context triple: [Trans-Canada Highway near Revelstoke, hasSafetyConcerns, winter driving conditions]
-
A.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
B.
safetyIssueHighlighted
chosen
Indicates that a particular safety concern or hazard has been identified and explicitly brought to attention.
-
C.
hasSecurityConsideration
Indicates that there is a relevant security-related issue, risk, or precaution associated with the referenced entity.
-
D.
observationSafety
Indicates that an observation or monitoring activity is conducted in a manner that ensures the safety of the subjects, observers, and environment involved.
-
E.
hasSafetyInformation
Indicates that one entity provides or is associated with safety-related details, warnings, or guidelines about another entity.
- 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_69e0b4b52c048190952b4d0f430813a3 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a5dd02588190abddfcb868259a38 |
completed | April 20, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e59fe5592c8190bb6122b784496d02 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:38 a.m.