Triple
T35636950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Group Rally2 |
E1029744
|
entity |
| Predicate | competitionExample |
P35643
|
FINISHED |
| Object | FIA WRC2 Championship |
—
|
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: FIA WRC2 Championship | Statement: [Group Rally2, competitionExample, FIA WRC2 Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionExample Context triple: [Group Rally2, competitionExample, FIA WRC2 Championship]
-
A.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
B.
competition
Indicates a relationship where two or more entities strive against each other to achieve a superior outcome, advantage, or reward.
-
C.
competitionUse
Indicates that one entity uses or engages in a competition involving another entity.
-
D.
competitionFrom
Indicates that one entity is experiencing competitive pressure or rivalry originating from another entity.
-
E.
competitionElement
chosen
Indicates that one entity is a component, phase, or sub-event within a larger competitive event or contest.
- 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_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:05 p.m.