Triple
T25618292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Percy Bentley |
E642218
|
entity |
| Predicate | ledTeamToPremiership |
P5917
|
FINISHED |
| Object | Richmond Football Club |
—
|
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 | Statement: [Percy Bentley, ledTeamToPremiership, Richmond Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledTeamToPremiership Context triple: [Percy Bentley, ledTeamToPremiership, Richmond Football Club]
-
A.
ledTeamToSuperBowl
Indicates that a person, acting as a team leader (such as a head coach or quarterback), guided their team to reach the Super Bowl game.
-
B.
ledTeamTo
chosen
Indicates that one entity acted as a leader or guiding force that directed a team toward achieving a particular goal, outcome, or success.
-
C.
ledTeamIn
Indicates that one entity had primary leadership responsibility over a team in which the other entity participated or was involved.
-
D.
teamManagedToPromotion
Indicates that a team successfully achieved promotion to a higher level, league, or division.
-
E.
wonPremiershipWith
Indicates that an entity achieved a premiership title while being a member of or associated with a particular team, club, or organization.
- 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.