Triple
T35636917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally2 |
E1029743
|
entity |
| Predicate | competitionClassRole |
P10053
|
FINISHED |
| Object | primary class for WRC2 |
—
|
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: primary class for WRC2 | Statement: [Rally2, competitionClassRole, primary class for WRC2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionClassRole Context triple: [Rally2, competitionClassRole, primary class for WRC2]
-
A.
competitionRole
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
-
B.
competitionClass
chosen
Indicates that one entity is classified into a particular competitive category or level within a competition or contest.
-
C.
participantClassification
Indicates how a participant in an event or interaction is categorized or typed with respect to their role or characteristics in that context.
-
D.
roleInRacingCalendar
Indicates the specific function or significance that a race or event holds within the overall racing calendar or season schedule.
-
E.
lineupRole
Indicates the specific role or position an entity holds within a lineup or ordered group.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:05 p.m.