Triple
T32805075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ihr Bild |
E838999
|
entity |
| Predicate | notableCycleCompanions |
P205162
|
FINISHED |
| Object | Ständchen (D 957) |
E838996
|
NE 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: Ständchen (D 957) | Statement: [Ihr Bild, notableCycleCompanions, Ständchen (D 957)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCycleCompanions Context triple: [Ihr Bild, notableCycleCompanions, Ständchen (D 957)]
-
A.
notableCycle
Indicates that there is a particularly significant or noteworthy recurring sequence or cycle involving the related entities.
-
B.
followsCycle
Indicates that one entity adheres to or repeats a recurring sequence, pattern, or cycle defined or exemplified by another entity.
-
C.
combinesCycle
Indicates that one entity merges or integrates its cycle with that of another entity to form a combined or unified cycle.
-
D.
tracksCycle
Indicates that one entity monitors, records, or follows the progression of another entity’s recurring cycle or periodic process.
-
E.
pairedCycle
Indicates a relationship where two cycles are associated or matched together as corresponding counterparts.
- F. None of above. chosen
Provenance (5 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34b178503081908a6880a045aa933f |
completed | June 19, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:15 a.m.