Triple
T29853833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death and the Maiden |
E758132
|
entity |
| Predicate | popularNicknameOf |
P22212
|
FINISHED |
| Object | String Quartet No. 14 in D minor, D 810 |
—
|
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: String Quartet No. 14 in D minor, D 810 | Statement: [Death and the Maiden, popularNicknameOf, String Quartet No. 14 in D minor, D 810]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularNicknameOf Context triple: [Death and the Maiden, popularNicknameOf, String Quartet No. 14 in D minor, D 810]
-
A.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
B.
hasNicknames
Indicates that an entity is known or referred to by one or more alternative informal names.
-
C.
unofficialNickname
Indicates that one entity is informally or colloquially known by a non-official nickname represented by the other entity.
-
D.
popularName
chosen
Indicates that the object is a commonly used or widely recognized name or nickname for the subject.
-
E.
childhoodNickname
Indicates that one entity is a nickname that was used to refer to the other entity during their childhood.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 5:45 p.m.