Triple
T22684554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASCAR Canada |
E560874
|
entity |
| Predicate | typeOfEventSanctioned |
P126417
|
FINISHED |
| Object | oval track racing |
—
|
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: oval track racing | Statement: [NASCAR Canada, typeOfEventSanctioned, oval track racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEventSanctioned Context triple: [NASCAR Canada, typeOfEventSanctioned, oval track racing]
-
A.
eventTypeSanctioned
chosen
Indicates that an event has been officially approved, authorized, or endorsed by a relevant authority.
-
B.
hasCoSanctionedEventWith
Indicates that two or more entities have jointly imposed or participated in the same sanction-related event or action.
-
C.
hasCoSanctionedEventsWith
Indicates that two entities have jointly sanctioned or approved the same events.
-
D.
sanctionedAs
Indicates that an entity is officially approved, authorized, or recognized in a particular role, status, or capacity by a relevant authority.
-
E.
typeOfEventManaged
Indicates that an entity is responsible for organizing, overseeing, or handling a specific category or kind of event.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17862c8a48190912a8ad09dfda795 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:12 p.m.