Triple
T14802168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craig Bellamy |
E347933
|
entity |
| Predicate | teamStatusAfterCoaching |
P115777
|
FINISHED |
| Object | one of the NRL’s most dominant clubs |
—
|
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: one of the NRL’s most dominant clubs | Statement: [Craig Bellamy, teamStatusAfterCoaching, one of the NRL’s most dominant clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamStatusAfterCoaching Context triple: [Craig Bellamy, teamStatusAfterCoaching, one of the NRL’s most dominant clubs]
-
A.
coachingTeam
Indicates that one entity serves as a coach or coaching staff for a particular team.
-
B.
teamCoachedReached
Indicates that a coach’s team successfully advanced to or reached a particular stage, event, or achievement.
-
C.
playerCoachTeam
Indicates a relationship where a player is coached by a specific coach while playing for a particular team.
-
D.
gameCoached
Indicates that one entity served as the coach for another entity in the context of a specific game or match.
-
E.
teamTypeCoached
Indicates the type or category of team that an individual has coached.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf30d044819082ac038e06481aab |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:31 a.m.