Triple
T24671087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chad Ochocinco |
E610834
|
entity |
| Predicate | legalNameChangeTo |
P60916
|
FINISHED |
| Object | Chad Javon Ochocinco |
—
|
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: Chad Javon Ochocinco | Statement: [Chad Ochocinco, legalNameChangeTo, Chad Javon Ochocinco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalNameChangeTo Context triple: [Chad Ochocinco, legalNameChangeTo, Chad Javon Ochocinco]
-
A.
officialNameChangeTo
Indicates that an entity’s official name has been changed from a previous name to a new specified name.
-
B.
changedSurnameFrom
Indicates that an entity has adopted a new surname that was previously a different, specified surname.
-
C.
changedSurnameTo
Indicates that an entity has adopted a new surname, replacing their previous one, with the new surname specified as the related entity.
-
D.
underwentNameChangeTo
chosen
Indicates that an entity previously known by one name has changed its name to the specified new name.
-
E.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
- 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 2:42 a.m.