Triple
T24442732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Rugby League World Cup |
E616311
|
entity |
| Predicate | notablePlayerOfTournament |
P23685
|
FINISHED |
| Object | Johnathan Thurston |
—
|
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: Johnathan Thurston | Statement: [2013 Rugby League World Cup, notablePlayerOfTournament, Johnathan Thurston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlayerOfTournament Context triple: [2013 Rugby League World Cup, notablePlayerOfTournament, Johnathan Thurston]
-
A.
playerOfTheTournament
chosen
Indicates that an entity has been recognized as the most outstanding performer in a particular tournament.
-
B.
notablePlayerInFinal
Indicates that a player had a significant or standout role in the final match or game of a competition.
-
C.
notableTournamentPerformance
Indicates that an entity achieved a significant or distinguished result or showing in a competitive tournament.
-
D.
notableTournament
Indicates that an entity is a tournament of particular significance or prominence in relation to another entity.
-
E.
notableWinner
Indicates that the subject is a particularly distinguished or prominent winner of the referenced competition, award, or contest.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2985129cc8190b5c99747d2dbcac8 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.