Triple
T19980585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonnet 18 |
E493805
|
entity |
| Predicate | closingCoupletFunction |
P124939
|
FINISHED |
| Object | asserts immortality through verse |
—
|
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: asserts immortality through verse | Statement: [Sonnet 18, closingCoupletFunction, asserts immortality through verse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closingCoupletFunction Context triple: [Sonnet 18, closingCoupletFunction, asserts immortality through verse]
-
A.
closingVerse
Indicates that one entity serves as the final or concluding verse of another entity, such as a song, poem, or hymn.
-
B.
closingSequenceFeature
chosen
Indicates a feature or element that appears specifically in the closing sequence of an event, process, or media item.
-
C.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
D.
closingInvocation
Indicates the act of formally concluding an event, process, or interaction, often with a final statement, command, or ritualized action.
-
E.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d12d968819081e315ec4585cd9f |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:28 p.m.