Triple
T33237785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Rugby Coach of the Year |
E850877
|
entity |
| Predicate | eligibleCoaches |
P142716
|
FINISHED |
| Object | national team coaches |
—
|
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: national team coaches | Statement: [World Rugby Coach of the Year, eligibleCoaches, national team coaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleCoaches Context triple: [World Rugby Coach of the Year, eligibleCoaches, national team coaches]
-
A.
eligibleCoachesFrom
chosen
Indicates that certain coaches are qualified or permitted to be selected or assigned from a specified source, group, or context.
-
B.
coachesInclude
Indicates that a set, group, or collection of coaches contains or includes a particular coach or subset of coaches.
-
C.
coachesFor
Indicates that one entity serves as a coach or trainer for another entity, typically providing guidance, instruction, or leadership in a specific activity or domain.
-
D.
coachesWith
Indicates that one entity serves as a coach or trainer in relation to another entity.
-
E.
featuredCoach
Indicates that a particular coach is highlighted or given special prominence within a specific context or collection.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:31 a.m.