Triple
T21340702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Cockell |
E526181
|
entity |
| Predicate | foughtForTitle |
P69999
|
FINISHED |
| Object | world heavyweight title |
—
|
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: world heavyweight title | Statement: [Don Cockell, foughtForTitle, world heavyweight title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foughtForTitle Context triple: [Don Cockell, foughtForTitle, world heavyweight title]
-
A.
foughtAs
Indicates that an entity participated in a conflict or war in the capacity, role, or identity specified by another entity.
-
B.
hasFoughtForTitle
chosen
Indicates that an entity has participated in a contest or event specifically for a championship or title.
-
C.
foughtForFaction
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
-
D.
foughtUnderRuler
Indicates that one entity engaged in combat or military service under the authority, command, or leadership of another entity (the ruler).
-
E.
laterFoughtAlongside
Indicates that two entities, who were previously in some other relationship or context, subsequently fought on the same side as allies in a conflict or battle.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8a84dfa04819097dbe21eb40a45ef |
completed | April 22, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:44 p.m.