Triple
T10224876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Cheika |
E243179
|
entity |
| Predicate | teamCoachedReached |
P92855
|
FINISHED |
| Object | 2015 Rugby World Cup final with Australia |
—
|
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: 2015 Rugby World Cup final with Australia | Statement: [Michael Cheika, teamCoachedReached, 2015 Rugby World Cup final with Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamCoachedReached Context triple: [Michael Cheika, teamCoachedReached, 2015 Rugby World Cup final with Australia]
-
A.
teamCoachedFrom
Indicates that a coaching relationship exists where a coach is responsible for training or managing a team originating from a specific organization, location, or context.
-
B.
teamCoachedToTitle
Indicates that a coach led a team to win a championship or title.
-
C.
teamTypeCoached
Indicates the type or category of team that an individual has coached.
-
D.
leagueCoachedIn
Indicates the league in which a person or coach has coached a team.
-
E.
teamAchievement
Indicates that a group of individuals collectively accomplished a shared goal or met a performance milestone.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d23a9c4c8190abece9e52879c479 |
completed | April 7, 2026, 9:45 a.m. |
Created at: April 6, 2026, 11:16 a.m.