Triple
T25879405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toby Nankervis |
E652004
|
entity |
| Predicate | coCaptainOf |
P114876
|
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: [Toby Nankervis, coCaptainOf, Richmond Football Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coCaptainOf Context triple: [Toby Nankervis, coCaptainOf, Richmond Football Club]
-
A.
coCaptain
chosen
Indicates that two or more individuals share the role and responsibilities of captain jointly.
-
B.
captain
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
C.
assistantCaptain
Indicates that one entity serves as the assistant or deputy to another entity who holds the role of captain.
-
D.
conferenceOfCaptain
Indicates that a conference or formal meeting is associated with, organized by, or held for a specific captain.
-
E.
laterCaptain
Indicates that one entity becomes the captain of something at a later time than another referenced captain or captaincy.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6033d54948190a52da9e6bef00afa |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:13 a.m.