Triple
T31755374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anyone Can Cook |
E810542
|
entity |
| Predicate | formatInUniverse |
P121019
|
FINISHED |
| Object | illustrated cookbook |
—
|
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: illustrated cookbook | Statement: [Anyone Can Cook, formatInUniverse, illustrated cookbook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatInUniverse Context triple: [Anyone Can Cook, formatInUniverse, illustrated cookbook]
-
A.
hasInUniverseFormat
chosen
Indicates that something is presented or expressed in a specific format as it exists within a particular fictional or conceptual universe.
-
B.
inUniverseForm
Indicates that an entity appears or exists in a particular form within a specified fictional universe or continuity.
-
C.
universeName
Indicates the name or designated title assigned to a particular universe or cosmic setting.
-
D.
namedAfterInUniverse
Indicates that one entity is, within the fictional or narrative universe, explicitly stated or implied to be named after another entity.
-
E.
inUniverseCulture
Indicates that a cultural practice, norm, or tradition exists within and is characteristic of a particular fictional or defined universe.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 30, 2026, 11:29 p.m.