Triple
T33926401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beschlüsse der Landessynode der Evangelischen Landeskirche in Württemberg |
E869762
|
entity |
| Predicate | Rechtsfolge |
P178390
|
FINISHED |
| Object | Bindung der kirchlichen Organe |
—
|
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: Bindung der kirchlichen Organe | Statement: [Beschlüsse der Landessynode der Evangelischen Landeskirche in Württemberg, Rechtsfolge, Bindung der kirchlichen Organe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Rechtsfolge Context triple: [Beschlüsse der Landessynode der Evangelischen Landeskirche in Württemberg, Rechtsfolge, Bindung der kirchlichen Organe]
-
A.
محاكمة
Indicates that a legal trial or judicial proceeding is being conducted involving the entities.
-
B.
מאפיין עונתי
Indicates that something exhibits a seasonal characteristic, pattern, or variation over time.
-
C.
يحكمها
Indicates that an entity governs, rules, or exercises authority over another entity.
-
D.
التأثير
Indicates a relationship where one entity produces a change or has an influence on another entity or its state.
-
E.
סיבת מוות
Indicates the cause or reason that led to an entity’s death.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7107acf0481909b01467b9ebbde01 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fb41a9c8190a121e62e510dc18a |
completed | May 3, 2026, 9:04 a.m. |
Created at: May 1, 2026, 1:49 a.m.