Triple
T22873262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Who Fears Death |
E567254
|
entity |
| Predicate | adaptationPlannedAs |
P150064
|
FINISHED |
| Object | television series |
—
|
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: television series | Statement: [Who Fears Death, adaptationPlannedAs, television series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptationPlannedAs Context triple: [Who Fears Death, adaptationPlannedAs, television series]
-
A.
plannedAdaptation
Indicates that an adaptation or modification has been intentionally designed or scheduled to occur in response to certain conditions or goals.
-
B.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
-
C.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
D.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
E.
governancePlannedAs
Indicates that a specific governance structure, process, or arrangement is intended or planned to be applied to an entity or context.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f55c4b88190adb49871e496ca54 |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:38 p.m.