Triple
T33498739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celador Group |
E857931
|
entity |
| Predicate | createdFormat |
P199025
|
FINISHED |
| Object | Who Wants to Be a Millionaire? television format |
—
|
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: Who Wants to Be a Millionaire? television format | Statement: [Celador Group, createdFormat, Who Wants to Be a Millionaire? television format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdFormat Context triple: [Celador Group, createdFormat, Who Wants to Be a Millionaire? television format]
-
A.
createdFormatThatBecame
Indicates that one entity created a format which later evolved into or was adopted as another specified format.
-
B.
usedFormat
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
-
C.
definesFormatFor
Indicates that one entity specifies or establishes the format or structural pattern to be used by another entity.
-
D.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
E.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
- F. None of above. chosen
Provenance (4 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69ff1ba7494481908678a7a0f93dbd03 |
completed | May 9, 2026, 11:33 a.m. |
Created at: May 1, 2026, 1:38 a.m.