Triple
T12290405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evander Holyfield |
E292941
|
entity |
| Predicate | heldTitleOf |
P20021
|
FINISHED |
| Object | undisputed cruiserweight world champion |
—
|
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: undisputed cruiserweight world champion | Statement: [Evander Holyfield, heldTitleOf, undisputed cruiserweight world champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldTitleOf Context triple: [Evander Holyfield, heldTitleOf, undisputed cruiserweight world champion]
-
A.
heldTitleFrom
Indicates that an entity possessed or held a particular title starting from a specified point in time.
-
B.
titleHeldAs
Indicates that an entity holds or possesses a specific title in a particular capacity or role.
-
C.
notableTitleHeld
chosen
Indicates that an entity has held a distinguished or noteworthy title, rank, or official position.
-
D.
heldTitleUntil
Indicates that an entity possessed or held a specific title or position continuously up to a particular end date or point in time.
-
E.
titleHeldAfter
Indicates that one entity held a particular title or position after another entity, establishing a temporal succession in holding that title.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9261e1570819084bb4fdb44aa6aea |
completed | April 10, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69d91c4d9a9c8190aeb7beaf9792d8f0 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.