Triple
T25233938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sye |
E632287
|
entity |
| Predicate | hasRugbyCoachCharacter |
P158054
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sye, hasRugbyCoachCharacter, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRugbyCoachCharacter Context triple: [Sye, hasRugbyCoachCharacter, yes]
-
A.
hasCoachCharacter
Indicates that one entity serves as the coach or trainer character associated with another entity.
-
B.
featuredCoach
Indicates that a particular coach is highlighted or given special prominence within a specific context or collection.
-
C.
coachOf
Indicates that one entity serves as the coach (trainer or manager) of another entity, typically a person or team.
-
D.
hasCoachOfCentre
Indicates that an entity serves as the coach associated with a particular centre.
-
E.
requiresCoach
Indicates that one entity depends on or must have the involvement, guidance, or supervision of a coach in order for an action, process, or state to occur or be valid.
- F. None of above. chosen
Provenance (4 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47df734648190b24eb3eea5b65dd6 |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 1:06 p.m.