Triple
T20223213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonnet 30 |
E495310
|
entity |
| Predicate | addresseeType |
P139285
|
FINISHED |
| Object | beloved friend |
—
|
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: beloved friend | Statement: [Sonnet 30, addresseeType, beloved friend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addresseeType Context triple: [Sonnet 30, addresseeType, beloved friend]
-
A.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
-
B.
addresseeDescription
Indicates that one entity provides a descriptive characterization or identifying information about the addressee of a communication or message.
-
C.
addressingType
Indicates the manner or form in which one entity addresses or refers to another (e.g., formally, informally, by title, or by name).
-
D.
addresseePosition
Indicates the spatial or positional relationship of the addressee relative to a reference point or speaker.
-
E.
addresseeStatus
Indicates the role, condition, or state of the entity that is the recipient or target of a communication or action.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd827708190b798a30f4e7d533f |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:39 p.m.