Triple
T35806814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Deadman |
E1035121
|
entity |
| Predicate | storylinePower |
P152071
|
FINISHED |
| Object | control over darkness |
—
|
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: control over darkness | Statement: [The Deadman, storylinePower, control over darkness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storylinePower Context triple: [The Deadman, storylinePower, control over darkness]
-
A.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
B.
powerLevelInStory
chosen
Indicates the relative strength or power a character or entity possesses within the context of a specific story or narrative.
-
C.
storylineTone
Indicates the overall emotional quality or mood conveyed by the storyline in relation to an entity.
-
D.
storylineReason
Indicates that one event, action, or situation occurs as a narrative cause or justification for another within a storyline.
-
E.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.