Triple
T31964758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Man Who Came Early |
E816141
|
entity |
| Predicate | themeContrastWith |
P7994
|
FINISHED |
| Object | Lest Darkness Fall |
—
|
NE NERFINISHED |
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: Lest Darkness Fall | Statement: [The Man Who Came Early, themeContrastWith, Lest Darkness Fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeContrastWith Context triple: [The Man Who Came Early, themeContrastWith, Lest Darkness Fall]
-
A.
themeContrast
chosen
Indicates a relationship where two themes are compared or opposed to highlight their differences or tension.
-
B.
themeChange
Indicates that an entity undergoes a change in its theme, style, or subject, typically transitioning from one thematic state or configuration to another.
-
C.
providesContrastWith
Indicates that one entity is used to highlight differences or distinctions when compared with another entity.
-
D.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
E.
achievesContrast
Indicates that one entity creates or enhances a visual or conceptual difference relative to another entity.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2e9f9f48190b52e9381133c102d |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:09 a.m.