Triple
T11424600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oz, the Great and Horrible |
E270713
|
entity |
| Predicate | taskDemands |
P7686
|
FINISHED |
| Object | killing the Wicked Witch of the West |
—
|
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: killing the Wicked Witch of the West | Statement: [Oz, the Great and Horrible, taskDemands, killing the Wicked Witch of the West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: taskDemands Context triple: [Oz, the Great and Horrible, taskDemands, killing the Wicked Witch of the West]
-
A.
workRequirement
Indicates that one entity imposes or specifies a condition related to work that another entity must fulfill.
-
B.
demands
chosen
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
C.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
D.
userTask
Indicates that a specific task is assigned to, owned by, or performed by a particular user.
-
E.
taskInPlot
Indicates that a specific task occurs within, is associated with, or is part of a particular plot or storyline.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806be9c2c819084da13101cbb6c81 |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.