Triple
T33237760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Rugby Coach of the Year |
E850877
|
entity |
| Predicate | firstWinnerTeamCoached |
P11367
|
FINISHED |
| Object | Australia national rugby union team |
E49061
|
NE 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: Australia national rugby union team | Statement: [World Rugby Coach of the Year, firstWinnerTeamCoached, Australia national rugby union team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWinnerTeamCoached Context triple: [World Rugby Coach of the Year, firstWinnerTeamCoached, Australia national rugby union team]
-
A.
firstWinnerTeam
chosen
Indicates that the referenced team is the one that secured first place or victory in a given competition or event.
-
B.
headCoachWinningTeam
Indicates that the subject is the head coach of the team that won a particular game, match, or competition.
-
C.
coachOfScoringTeam
Indicates that one entity is the coach of the team that scored in a particular play or event.
-
D.
winningTeam
Indicates which team is the victor in a given competition, game, or contest.
-
E.
teamOfWinningCoach
Indicates the team that is coached by the coach who won (e.g., a game, season, or championship).
- F. None of above.
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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a352fd7a74081909ed291cc0289c599 |
completed | June 19, 2026, 12:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:31 a.m.