Triple
T30068899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | To Clarinda, on Hearing She Was Ill |
E764119
|
entity |
| Predicate | addresseeAlias |
P171066
|
FINISHED |
| Object | Clarinda |
—
|
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: Clarinda | Statement: [To Clarinda, on Hearing She Was Ill, addresseeAlias, Clarinda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addresseeAlias Context triple: [To Clarinda, on Hearing She Was Ill, addresseeAlias, Clarinda]
-
A.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
-
B.
addresseePseudonym
chosen
Indicates that the referenced name is a pseudonym used for the addressee in the context of the described communication or interaction.
-
C.
addresseeType
Indicates the role or category of the entity that is the intended recipient or target of a communication or message.
-
D.
addresseeDescription
Indicates that one entity provides a descriptive characterization or identifying information about the addressee of a communication or message.
-
E.
subjectAlias
Indicates that one entity is an alternative name, label, or alias referring to the same subject as 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 7 p.m.