Triple
T19153553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Do not go gentle into that good night |
E468867
|
entity |
| Predicate | imperativePhrase |
P25671
|
FINISHED |
| Object | Do not go gentle |
—
|
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: Do not go gentle | Statement: [Do not go gentle into that good night, imperativePhrase, Do not go gentle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imperativePhrase Context triple: [Do not go gentle into that good night, imperativePhrase, Do not go gentle]
-
A.
containsImperative
chosen
Indicates that one entity (typically a text or utterance) includes an imperative expression directing or commanding an action.
-
B.
hasImperativeEnding
Indicates that an expression concludes with a verb form or construction that conveys an imperative (command or directive) mood.
-
C.
invocationWord
Indicates that a specific word or phrase is used to call upon, activate, or summon an entity, power, or process.
-
D.
imposes
Indicates that one entity enforces, applies, or places a rule, condition, burden, or obligation upon another entity.
-
E.
mainPhrase
Indicates that the referenced phrase functions as the primary or central phrase within a larger linguistic or structural unit.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb7575c8190b52a9d2bde5ac288 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.