Triple
T19980743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonnet 73 |
E493808
|
entity |
| Predicate | hasQuatrain3Image |
P138155
|
FINISHED |
| Object | glowing embers on a dying fire |
—
|
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: glowing embers on a dying fire | Statement: [Sonnet 73, hasQuatrain3Image, glowing embers on a dying fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuatrain3Image Context triple: [Sonnet 73, hasQuatrain3Image, glowing embers on a dying fire]
-
A.
hasPhotographs
Indicates that one entity possesses, contains, or is associated with one or more photographs of another entity or subject.
-
B.
hasPhotograph
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
-
C.
containsImage
Indicates that one entity includes or embeds an image as part of its content or structure.
-
D.
hasPortrait
Indicates that one entity possesses, displays, or is associated with a portrait depicting another entity.
-
E.
notableQuatrain
Indicates that the subject is a four-line verse (quatrain) that is recognized as notable, significant, or especially well-known.
- 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_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. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 11, 2026, 3:28 p.m.