Triple
T38599750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elvira Madigan |
E934175
|
entity |
| Predicate | movementAssociatedWithNickname |
P193039
|
FINISHED |
| Object | second movement |
—
|
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: second movement | Statement: [Elvira Madigan, movementAssociatedWithNickname, second movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementAssociatedWithNickname Context triple: [Elvira Madigan, movementAssociatedWithNickname, second movement]
-
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.
hasNicknamedEntityType
Indicates that an entity is associated with another entity type specifically in the role of being its nickname or informal name.
-
D.
notableNickname
Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
-
E.
dedicatedToOrNicknameOf
Indicates that one entity is either the dedicatee of something (e.g., a work, object, or honor) or serves as an alternative name or nickname for 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
| PDg | Predicate description generation | batch_69fd35d029588190a525aa8a506e7708 |
completed | May 8, 2026, 1:01 a.m. |
Created at: May 3, 2026, 4:32 p.m.