Triple
T30634880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cole Sear |
E779810
|
entity |
| Predicate | hasNightmaresAbout |
P122350
|
FINISHED |
| Object | dead people |
—
|
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: dead people | Statement: [Cole Sear, hasNightmaresAbout, dead people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNightmaresAbout Context triple: [Cole Sear, hasNightmaresAbout, dead people]
-
A.
hasRecurringNightmareAbout
chosen
Indicates that one entity repeatedly experiences disturbing dreams centered on or involving another entity.
-
B.
hasDreamFrom
Indicates that an entity experiences or receives a dream that originates from another entity or source.
-
C.
hasDreamingBeliefs
Indicates that an entity holds beliefs, views, or assumptions specifically about dreams or the nature of dreaming.
-
D.
hasSupernaturalExperience
Indicates that an entity undergoes or has undergone an event or state involving phenomena beyond normal natural or scientific explanation.
-
E.
haunts
Indicates that one entity persistently appears in, lingers around, or psychologically troubles another entity or place, often in a recurring or unsettling way.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a5062f08190be313f1baa1a317d |
completed | May 2, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:28 p.m.