Triple
T23648052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Who Wants to Be a Millionaire (U.S. syndicated version) |
E584090
|
entity |
| Predicate | succeededByHost |
P142002
|
FINISHED |
| Object | Cedric the Entertainer |
—
|
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: Cedric the Entertainer | Statement: [Who Wants to Be a Millionaire (U.S. syndicated version), succeededByHost, Cedric the Entertainer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByHost Context triple: [Who Wants to Be a Millionaire (U.S. syndicated version), succeededByHost, Cedric the Entertainer]
-
A.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
B.
succeededByName
Indicates that one entity is followed or replaced by another entity identified by a specific name.
-
C.
succeededByEvent
Indicates that one event directly follows and replaces another in a temporal or sequential order.
-
D.
succeededByContext
Indicates that one context or situation directly follows and replaces another in a sequence or progression.
-
E.
holderSucceededAs
chosen
Indicates that one holder of a position, title, or role directly followed and replaced another as their successor.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b287606881909926de5efd882a76 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.