Triple
T11590287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anhalt-Cöthen |
E274861
|
entity |
| Predicate | hasCourtOfficial |
P100472
|
FINISHED |
| Object | Kapellmeister |
—
|
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: Kapellmeister | Statement: [Anhalt-Cöthen, hasCourtOfficial, Kapellmeister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtOfficial Context triple: [Anhalt-Cöthen, hasCourtOfficial, Kapellmeister]
-
A.
courtOfficial
Indicates that an entity serves in an official capacity within a court, holding an authorized role in judicial or legal proceedings.
-
B.
hasJudicialOfficer
Indicates that an entity is associated with or served by a specific judicial officer (such as a judge or magistrate) responsible for legal or court-related functions.
-
C.
hasPrincipalJudge
Indicates that one entity serves as the main or presiding judge for another entity, such as a court or judicial body.
-
D.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
E.
hasSeniorJudge
Indicates that one entity is assigned or linked to another entity serving in the role of a senior judge.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d894643ae48190837502b713f5b9c6 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.