Triple
T32492258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Rugby Women’s 15s Player of the Year |
E830419
|
entity |
| Predicate | notableWinnerCountry |
P18319
|
FINISHED |
| Object | Canada |
E14901
|
NE 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: Canada | Statement: [World Rugby Women’s 15s Player of the Year, notableWinnerCountry, Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWinnerCountry Context triple: [World Rugby Women’s 15s Player of the Year, notableWinnerCountry, Canada]
-
A.
notableWinner
Indicates that the subject is a particularly distinguished or prominent winner of the referenced competition, award, or contest.
-
B.
winnerCountry
chosen
Indicates the country that achieved first place or victory in a given competition, event, or contest.
-
C.
nationalityOfWinner
Indicates the country or nationality associated with the winner of a given event or competition.
-
D.
notableHolderCountry
Indicates that a country is recognized as a significant or notable holder of a particular item, title, record, or distinction.
-
E.
notableFirstWinner
Indicates that the subject is the first and notably recognized winner of the object (such as an award, competition, or title).
- F. None of above.
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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34668bd50081908b32e4146b494e49 |
completed | June 18, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:59 a.m.