Triple
T35753039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIACR |
E1033365
|
entity |
| Predicate | regulatedCompetitionType |
P71842
|
FINISHED |
| Object | European Grand Prix |
—
|
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: European Grand Prix | Statement: [AIACR, regulatedCompetitionType, European Grand Prix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatedCompetitionType Context triple: [AIACR, regulatedCompetitionType, European Grand Prix]
-
A.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
B.
overseesCompetitionType
chosen
Indicates that one entity has responsibility for supervising, managing, or regulating a particular type or category of competition.
-
C.
officialCompetition
Indicates that there is a formally recognized or sanctioned competition relationship between the entities.
-
D.
associatedCompetitionType
Indicates that one entity is linked to or involved with a particular type or category of competition.
-
E.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:06 p.m.