Triple
T25618302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Percy Bentley |
E642218
|
entity |
| Predicate | teamCoachedInLeague |
P7104
|
FINISHED |
| Object | Richmond Football Club in the VFL |
—
|
NE NERFINISHED |
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: Richmond Football Club in the VFL | Statement: [Percy Bentley, teamCoachedInLeague, Richmond Football Club in the VFL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamCoachedInLeague Context triple: [Percy Bentley, teamCoachedInLeague, Richmond Football Club in the VFL]
-
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.
leagueCoachedIn
chosen
Indicates the league in which a person or coach has coached a team.
-
C.
teamTypeCoached
Indicates the type or category of team that an individual has coached.
-
D.
teamCoachedReached
Indicates that a coach’s team successfully advanced to or reached a particular stage, event, or achievement.
-
E.
associatedLeagueTeam
Indicates that one entity is a sports team that is formally linked or affiliated with a particular league.
- 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_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 5:02 p.m.