Triple
T34362880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elegy on the Death of Mr. Handel |
E881924
|
entity |
| Predicate | hasDedicateeOccupation |
P189795
|
FINISHED |
| Object | composer |
—
|
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: composer | Statement: [Elegy on the Death of Mr. Handel, hasDedicateeOccupation, composer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDedicateeOccupation Context triple: [Elegy on the Death of Mr. Handel, hasDedicateeOccupation, composer]
-
A.
dedicateeOccupation
chosen
Indicates the occupation or professional role of the person to whom something (such as a work, object, or honor) is dedicated.
-
B.
hasOccupationOfDesignee
Indicates that one entity serves as the designated or appointed holder of an occupation or role for another entity.
-
C.
hasOccupationAttribute
Indicates that an entity possesses a specific characteristic, quality, or attribute related to its occupation or job.
-
D.
dedicateeRole
Indicates the specific role or capacity in which a person is honored or addressed as the dedicatee of a work or object.
-
E.
endedOccupationOf
Indicates that one entity brought another entity’s occupation or control of a place or position to an end.
- 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 1, 2026, 1:58 a.m.