Triple
T24580137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby League World Cup 9s |
E608224
|
entity |
| Predicate | winner2019Men |
P69743
|
FINISHED |
| Object | Australia national rugby league team |
—
|
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: Australia national rugby league team | Statement: [Rugby League World Cup 9s, winner2019Men, Australia national rugby league team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winner2019Men Context triple: [Rugby League World Cup 9s, winner2019Men, Australia national rugby league team]
-
A.
men'sSinglesChampion
Indicates that the subject is the winner of the men's singles competition in a given event or tournament.
-
B.
2019Winner
chosen
Indicates that the subject is the entity that won a specified competition, award, or event in the year 2019.
-
C.
winnerGender
Indicates the gender of the entity that is the winner in a given event or competition.
-
D.
doubleWinner
Indicates that the same entity has won the relevant award, contest, or recognition twice.
-
E.
notableCompetitorMen
Indicates that there is a notable male competitor associated with the subject in a competitive context.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a97fde9c81909d8de91b6358a015 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.