Triple
T26505952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TCR International Series |
E669543
|
entity |
| Predicate | teamsChampionship |
P123295
|
FINISHED |
| Object | TCR International Series Teams' 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: TCR International Series Teams' Championship | Statement: [TCR International Series, teamsChampionship, TCR International Series Teams' Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamsChampionship Context triple: [TCR International Series, teamsChampionship, TCR International Series Teams' Championship]
-
A.
teamChampionshipsWon
Indicates the number of championship titles that a team has won.
-
B.
teamChampionshipName
chosen
Indicates the name or title of the championship associated with a particular team.
-
C.
team2ChampionshipHistory
Indicates the record of championships that the second team has participated in or won over time.
-
D.
championshipWithTeam
Indicates that an entity has won or holds a championship title specifically while being a member of a particular team.
-
E.
teamInChampionship
Indicates that a particular team is participating in or is a contender within a specified championship event.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6138d906c81909258a45100e098be |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:16 a.m.