Triple
T33926412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grundsätze der kirchlichen Disziplinarordnung |
E869763
|
entity |
| Predicate | hatRechtscharakter |
P177915
|
FINISHED |
| Object | innerkirchliche Satzung |
—
|
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: innerkirchliche Satzung | Statement: [Grundsätze der kirchlichen Disziplinarordnung, hatRechtscharakter, innerkirchliche Satzung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatRechtscharakter Context triple: [Grundsätze der kirchlichen Disziplinarordnung, hatRechtscharakter, innerkirchliche Satzung]
-
A.
hatCharakter
Indicates that an entity possesses or exhibits a particular character, trait, or quality.
-
B.
gehörtZuRechtsgebiet
Indicates that something is assigned or belongs to a particular legal field or area of law.
-
C.
karakter
Indicates that one entity is a character (e.g., a role or persona) associated with or embodied by another entity.
-
D.
heldRight
Indicates that one entity is being held on the right side of another entity.
-
E.
hatBezugZu
chosen
Indicates that one entity has a (often contextual or referential) relation or connection to another 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:49 a.m.