Triple
T19245921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yorkton Terriers |
E481253
|
entity |
| Predicate | wonNationalTitle |
P135046
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Yorkton Terriers, wonNationalTitle, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonNationalTitle Context triple: [Yorkton Terriers, wonNationalTitle, 2014]
-
A.
wonWorldTitleIn
Indicates that an entity achieved victory in a world championship title in a specified competition or year.
-
B.
wonTitleFrom
Indicates that one entity obtained a title or championship by defeating or surpassing another specific entity who previously held it.
-
C.
wonTitleWith
Indicates that an entity secured a specific title, award, or championship while being associated with or representing another entity (such as a team, organization, or group).
-
D.
wonLeagueTitle
Indicates that a team or individual finished a competition as champions, securing the league title for that season or tournament.
-
E.
winnerTitle
Indicates the formal title or designation awarded to the entity that wins a particular competition, contest, or event.
- F. None of above. chosen
Provenance (4 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb2c34e88190a338e5a7ba906425 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:27 p.m.