Triple
T467703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Long Dark Tea-Time of the Soul |
E8484
|
entity |
| Predicate | hasMotiveElement |
P15083
|
FINISHED |
| Object | supernatural events |
—
|
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: supernatural events | Statement: [The Long Dark Tea-Time of the Soul, hasMotiveElement, supernatural events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotiveElement Context triple: [The Long Dark Tea-Time of the Soul, hasMotiveElement, supernatural events]
-
A.
hasMandate
Indicates that an entity is officially authorized or required to perform a specific role, action, or set of responsibilities.
-
B.
hasMomentumState
Indicates that an entity possesses a particular state or condition related to its momentum (e.g., magnitude, direction, or dynamic status).
-
C.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
D.
hasProposedCause
Indicates that one entity is suggested or hypothesized to be the cause or explanation for another entity or event.
-
E.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd9bea081909ee782840f3da12b |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edebb3988190907992a584b4e260 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef257a548190a96bfa0cf6183976 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.