Triple
T32951096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allison DuBois |
E842952
|
entity |
| Predicate | hasDreamsAbout |
P94725
|
FINISHED |
| Object | future crimes |
—
|
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: future crimes | Statement: [Allison DuBois, hasDreamsAbout, future crimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDreamsAbout Context triple: [Allison DuBois, hasDreamsAbout, future crimes]
-
A.
hasDreamFrom
Indicates that an entity experiences or receives a dream that originates from another entity or source.
-
B.
hasNightmares
Indicates that an entity experiences disturbing or frightening dreams, typically during sleep.
-
C.
hasDreamingBeliefs
Indicates that an entity holds beliefs, views, or assumptions specifically about dreams or the nature of dreaming.
-
D.
hasRecurringNightmareAbout
Indicates that one entity repeatedly experiences disturbing dreams centered on or involving another entity.
-
E.
dreamsSignified
chosen
Indicates that one entity’s dreams symbolically represent, foreshadow, or convey information about another entity or situation.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d143c38c8190a6076ae13f6c6a4c |
completed | May 3, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.