Triple
T3768581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakar Rally |
E82739
|
entity |
| Predicate | hasNotableRisk |
P16293
|
FINISHED |
| Object | competitor fatalities |
—
|
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: competitor fatalities | Statement: [Dakar Rally, hasNotableRisk, competitor fatalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRisk Context triple: [Dakar Rally, hasNotableRisk, competitor fatalities]
-
A.
hasNotableHazard
chosen
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
B.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
-
C.
hasNotableImpact
Indicates that one entity exerts a significant or noteworthy influence or effect on another entity or context.
-
D.
hasNotableIncident
Indicates that an entity is associated with a significant or noteworthy event, occurrence, or incident.
-
E.
hasNotablePolicy
Indicates that an entity possesses a policy that is distinguished, significant, or otherwise noteworthy in its context.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2d4b848190bf63fb3ed5d3b2d9 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.