Triple
T23419731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Wagon Wheel |
E560616
|
entity |
| Predicate | rivalryTrophyIntroducedYear |
P40941
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [Battle of the Wagon Wheel, rivalryTrophyIntroducedYear, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryTrophyIntroducedYear Context triple: [Battle of the Wagon Wheel, rivalryTrophyIntroducedYear, 1946]
-
A.
hasRivalryTrophyStatus
Indicates that a rivalry trophy has a particular status or condition within the context of a competitive relationship.
-
B.
isRivalryTrophyFor
Indicates that an object serves as the trophy awarded in a rivalry competition between specific entities.
-
C.
trophyContestedBy
Indicates that a particular trophy is the object of competition among the specified participants or teams.
-
D.
isFormerChampionshipTrophyOf
Indicates that an object previously served as the official championship trophy awarded for a particular competition or title.
-
E.
trophyIntroducedInSeason
chosen
Indicates the season in which a particular trophy was first introduced or became part of a competition or series.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54489d48190b2b2c29701851765 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:44 p.m.