Triple
T34513034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Eales Medal |
E886074
|
entity |
| Predicate | notableNamesakeRole |
P133817
|
FINISHED |
| Object | former Wallabies captain |
—
|
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: former Wallabies captain | Statement: [John Eales Medal, notableNamesakeRole, former Wallabies captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNamesakeRole Context triple: [John Eales Medal, notableNamesakeRole, former Wallabies captain]
-
A.
hasFamousNamesakeRole
Indicates that an entity has a role or position that shares its name with a well-known or historically notable person.
-
B.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
-
C.
notableBearerOfRole
Indicates that an entity is a particularly prominent or well-known holder or performer of a specified role.
-
D.
notableNamesakeOccupation
chosen
Indicates that an entity is named after a notable person whose occupation or professional role is specified by the related value.
-
E.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.