Triple
T11473712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Chef America |
E271972
|
entity |
| Predicate | inspiredBy |
P9
|
FINISHED |
| Object | Iron Chef |
E927435
|
NE 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: Iron Chef | Statement: [Iron Chef America, inspiredBy, Iron Chef]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Iron Chef Context triple: [Iron Chef America, inspiredBy, Iron Chef]
-
A.
Iron Chef
chosen
Iron Chef is a Japanese cooking show franchise in which top chefs engage in timed, themed culinary battles before a panel of judges.
-
B.
Iron Chef America
Iron Chef America is a competitive cooking television series in which top chefs face off in timed culinary battles judged on creativity, taste, and presentation.
-
C.
Home Chef
Home Chef is a meal kit and prepared meals company offering convenient, ready-to-cook and heat-and-eat food solutions for home consumers.
-
D.
The Next Iron Chef
The Next Iron Chef is a reality cooking competition series in which top chefs compete in culinary challenges to earn the title of Iron Chef.
-
E.
Chef!
Chef! is a British television sitcom starring Lenny Henry as an irascible head chef running a high-end restaurant kitchen.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294b3f388190a587c358313f7260 |
completed | April 9, 2026, 10:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6042507c4819096afc2839fda186d |
completed | April 20, 2026, 10:47 a.m. |
Created at: April 8, 2026, 9:35 p.m.