Triple
T10254394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand rugby league |
E240424
|
entity |
| Predicate | elitePlayerPathway |
P18155
|
FINISHED |
| Object | New Zealand Warriors system |
—
|
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: New Zealand Warriors system | Statement: [New Zealand rugby league, elitePlayerPathway, New Zealand Warriors system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elitePlayerPathway Context triple: [New Zealand rugby league, elitePlayerPathway, New Zealand Warriors system]
-
A.
hasPlayerPathway
chosen
Indicates that there is a defined developmental or progression route available for a player within a given context or system.
-
B.
clubCareerStart
Indicates the point in time when an entity begins its professional or organized club-level career.
-
C.
careerStartAsPlayer
Indicates the point in time or context when an individual began their professional career as a player.
-
D.
professionalPlayersAllowedFrom
Indicates that professional players are permitted to participate starting from a specified point, such as a date, level, or stage.
-
E.
eliteField
Indicates that the entity is associated with a highly selective or top-tier field, domain, or area of specialization.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:30 a.m.