Triple
T30068863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarinda, mistress of my soul |
E764118
|
entity |
| Predicate | addresseePseudonym |
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: [Clarinda, mistress of my soul, addresseePseudonym, Clarinda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addresseePseudonym Context triple: [Clarinda, mistress of my soul, addresseePseudonym, Clarinda]
-
A.
pseudonymousAttribution
Indicates that an action, work, or statement is attributed to an entity using a pseudonym rather than their real identity.
-
B.
usedPseudonym
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
-
C.
pseudonymCoinedBy
Indicates that a particular pseudonym was created or invented by a specific agent or source.
-
D.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
-
E.
pseudonymousProducerIs
Indicates that one entity is the pseudonymous producer (creator operating under a pseudonym) of another entity.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 7 p.m.