Triple
T25618248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Yze |
E642216
|
entity |
| Predicate | coachingDiscipline |
P94050
|
FINISHED |
| Object | Australian rules football |
—
|
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: Australian rules football | Statement: [Adam Yze, coachingDiscipline, Australian rules football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachingDiscipline Context triple: [Adam Yze, coachingDiscipline, Australian rules football]
-
A.
coachingSpecialty
Indicates that a coach focuses on or is specialized in a particular area, topic, or type of coaching.
-
B.
coachingTrait
Indicates that one entity possesses a characteristic, style, or quality specifically related to coaching.
-
C.
coachingBase
Indicates a foundational coaching relationship in which one entity serves as the primary coach or mentor for another.
-
D.
coachingAt
Indicates that one entity is serving as a coach at, or providing coaching services within, a particular organization, institution, or location.
-
E.
hasCoachedDiscipline
chosen
Indicates that a person has coached or provided training in a particular discipline, field, or area of expertise.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa1e8d948190aab191bfa2226fb8 |
completed | May 2, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 5:02 p.m.