Triple
T6185427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand National |
E138042
|
entity |
| Predicate | famousIncident |
P25528
|
FINISHED |
| Object | 1993 void race due to false start |
—
|
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: 1993 void race due to false start | Statement: [Grand National, famousIncident, 1993 void race due to false start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousIncident Context triple: [Grand National, famousIncident, 1993 void race due to false start]
-
A.
famousForEvent
chosen
Indicates that an entity is widely known or recognized specifically because of a particular event.
-
B.
notableSubevent
Indicates that one event is a particularly significant or noteworthy component within a larger, encompassing event.
-
C.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
D.
notableEncounterWith
Indicates that an entity has had a significant or noteworthy meeting, interaction, or confrontation with another entity.
-
E.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062150fc48190877240abe6b6c636 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.