Triple
T32335092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landessynode |
E826149
|
entity |
| Predicate | istZentralesOrganVon |
P11117
|
FINISHED |
| Object | Evangelische Kirche in Mitteldeutschland |
—
|
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: Evangelische Kirche in Mitteldeutschland | Statement: [Landessynode, istZentralesOrganVon, Evangelische Kirche in Mitteldeutschland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: istZentralesOrganVon Context triple: [Landessynode, istZentralesOrganVon, Evangelische Kirche in Mitteldeutschland]
-
A.
hasCentralOrgan
Indicates that an entity possesses a primary or main organ that serves as a central functional or structural component.
-
B.
mainOrganOf
chosen
Indicates that one entity is the primary or central organ responsible for the core functions of another entity (such as an organism or system).
-
C.
имеетОрган
Indicates that one entity possesses or contains a specific organ as a part of its body.
-
D.
isCentralAdministrativeBodyOf
Indicates that one entity serves as the main governing or coordinating administrative authority for another entity or system.
-
E.
organLocation
Indicates the anatomical location or position of an organ within a body or organism.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be1779cc8190abe386c03d31d385 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6b633e0c88190a727bb7d2751e2d5 |
completed | May 3, 2026, 2:43 a.m. |
Created at: May 1, 2026, 12:48 a.m.