Triple
T28550691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie White |
E722876
|
entity |
| Predicate | hasCoachRole |
P119524
|
FINISHED |
| Object | figure skating coach |
—
|
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: figure skating coach | Statement: [Charlie White, hasCoachRole, figure skating coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoachRole Context triple: [Charlie White, hasCoachRole, figure skating coach]
-
A.
isActiveAsCoach
Indicates that an entity is currently functioning in the role of a coach within a given context or organization.
-
B.
associatedWithCoachRole
chosen
Indicates that an entity has a relationship involving the role or function of a coach, such as serving as, working as, or being linked to a coaching position.
-
C.
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.
-
D.
hasCoachCharacter
Indicates that one entity serves as the coach or trainer character associated with another entity.
-
E.
hasCoachedIn
Indicates that one entity has served as a coach in a particular context, such as for a team, organization, event, or location.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: April 28, 2026, 3:42 a.m.