Triple
T36318901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pocono Raceway |
E894274
|
entity |
| Predicate | hasPrimarySanctioningBody |
P149237
|
FINISHED |
| Object | NASCAR |
E25568
|
NE 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: NASCAR | Statement: [Pocono Raceway, hasPrimarySanctioningBody, NASCAR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySanctioningBody Context triple: [Pocono Raceway, hasPrimarySanctioningBody, NASCAR]
-
A.
isSanctionedBy
Indicates that an entity is subject to official penalties, restrictions, or punitive measures imposed by another authority or organization.
-
B.
laterSanctioningBody
chosen
Indicates that one entity serves as a subsequent or replacement sanctioning authority for another entity or event.
-
C.
otherMajorSanctioningBodies
Indicates that there exist additional significant organizations or authorities, beyond a primary one, that impose or administer sanctions.
-
D.
appliedSanctionsTo
Indicates that one entity has imposed sanctions or punitive restrictions on another entity.
-
E.
typeOfSanctionsAuthority
Indicates the authority or legal basis under which specific sanctions are imposed or administered.
- F. None of above.
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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d8e25448190b5538da8f4490f20 |
completed | June 22, 2026, 6:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.