Triple
T11475250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leopold, Prince of Anhalt-Cöthen |
E272009
|
entity |
| Predicate | courtChapelType |
P68935
|
FINISHED |
| Object | largely secular court chapel |
—
|
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: largely secular court chapel | Statement: [Leopold, Prince of Anhalt-Cöthen, courtChapelType, largely secular court chapel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtChapelType Context triple: [Leopold, Prince of Anhalt-Cöthen, courtChapelType, largely secular court chapel]
-
A.
hasChapelStyle
Indicates that a chapel possesses or is characterized by a particular architectural or stylistic design.
-
B.
hasChapelUse
chosen
Indicates that something is used, designated, or functions as a chapel or for chapel-related purposes.
-
C.
hasChapels
Indicates that one entity contains, includes, or is associated with one or more chapels.
-
D.
hasChurchType
Indicates that one entity (typically a church) is classified as being of a particular church type or category.
-
E.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
- 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.