Triple
T10254416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand rugby league |
E240424
|
entity |
| Predicate | hasJuniorPathway |
P18155
|
FINISHED |
| Object | club junior grades |
—
|
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: club junior grades | Statement: [New Zealand rugby league, hasJuniorPathway, club junior grades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJuniorPathway Context triple: [New Zealand rugby league, hasJuniorPathway, club junior grades]
-
A.
hasJuniorSection
Indicates that an entity includes or is associated with a subordinate or lower-level section within its structure or organization.
-
B.
hasJuniorStatus
Indicates that one entity holds a lower, subordinate, or less senior status relative to another entity within a defined hierarchy or context.
-
C.
hasPlayerPathway
chosen
Indicates that there is a defined developmental or progression route available for a player within a given context or system.
-
D.
hasJuniorSystem
Indicates that an entity has another entity associated with it in a subordinate or lower-level system role or configuration.
-
E.
hasPathway
Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
- 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.