Triple
T27658948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Prix of Portland |
E697066
|
entity |
| Predicate | mainSanctioningBody |
P104360
|
FINISHED |
| Object | INDYCAR LLC |
—
|
NE NERFINISHED |
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: INDYCAR LLC | Statement: [Grand Prix of Portland, mainSanctioningBody, INDYCAR LLC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSanctioningBody Context triple: [Grand Prix of Portland, mainSanctioningBody, INDYCAR LLC]
-
A.
laterSanctioningBody
Indicates that one entity serves as a subsequent or replacement sanctioning authority for another entity or event.
-
B.
fullSanctioningBodyName
chosen
Indicates that the object is the complete, official name of the organization that authoritatively sanctions or governs the subject.
-
C.
otherMajorSanctioningBodies
Indicates that there exist additional significant organizations or authorities, beyond a primary one, that impose or administer sanctions.
-
D.
organizationTypeOfSanctioningBody
Indicates the type or category of organization that serves as the sanctioning body in a given context.
-
E.
typeOfSanctionsAuthority
Indicates the authority or legal basis under which specific sanctions are imposed or administered.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:35 p.m.