Triple
T11475257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold, Prince of Anhalt-Cöthen |
E272009
|
entity |
| Predicate | patronagePeriodOfBach |
P65841
|
FINISHED |
| Object | 1717–1723 |
—
|
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: 1717–1723 | Statement: [Leopold, Prince of Anhalt-Cöthen, patronagePeriodOfBach, 1717–1723]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronagePeriodOfBach Context triple: [Leopold, Prince of Anhalt-Cöthen, patronagePeriodOfBach, 1717–1723]
-
A.
employedAsKapellmeister
Indicates that one entity is employed in the role or position of Kapellmeister (music director/chapel master) for another entity.
-
B.
honoursPeriod
Indicates the time span during which an honour, award, or recognition is valid, held, or in effect for an entity.
-
C.
collaborationPeriod
chosen
Indicates the time span during which two or more entities are actively engaged in a collaborative relationship or joint activity.
-
D.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
-
E.
seasonSpan
Indicates the time period or range of dates over which a particular season extends or is in effect.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294c8dc48190a515f83c99405a3b |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.