Triple
T13093112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Club Championship |
E310512
|
entity |
| Predicate | winnerDetermines |
P3221
|
FINISHED |
| Object | world club champion in rugby league |
—
|
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: world club champion in rugby league | Statement: [World Club Championship, winnerDetermines, world club champion in rugby league]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerDetermines Context triple: [World Club Championship, winnerDetermines, world club champion in rugby league]
-
A.
winnerManager
Indicates that one entity is the manager or supervisor of another entity who is the winner in a given context or competition.
-
B.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
C.
winnerThrows
Indicates that the entity identified as the winner performs or executes a throw action toward or involving another entity.
-
D.
winnerType
Indicates the category or kind of winner associated with an event, competition, or outcome.
-
E.
decidingGameWinner
chosen
Indicates that an event, action, or process determines which participant is the winner of a game.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9813cd1b881909871a318fdd60672 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.