Triple
T29010560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasche-Mann |
E736553
|
entity |
| Predicate | dedicatedWorkCycleTo |
P49437
|
FINISHED |
| Object | Clara Wieck |
—
|
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: Clara Wieck | Statement: [Hasche-Mann, dedicatedWorkCycleTo, Clara Wieck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedWorkCycleTo Context triple: [Hasche-Mann, dedicatedWorkCycleTo, Clara Wieck]
-
A.
dedicatedCycleTo
Indicates that a particular cycle, period, or iteration is specifically allocated or reserved for a given purpose, task, or entity.
-
B.
workBelongsToCycle
Indicates that a specific work is associated with, and forms part of, a larger cycle or series.
-
C.
hasWorkDedicatedTo
chosen
Indicates that one entity has a work (such as a book, artwork, or composition) that is formally dedicated to another entity.
-
D.
mainWorkPeriod
Indicates the primary or most significant span of time during which an entity is active, employed, or engaged in a particular work or role.
-
E.
namedForWorkOn
Indicates that an entity is named in honor of another entity specifically because of that entity’s work or contributions in a particular field or endeavor.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 9:42 a.m.