Triple
T32335108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landessynode |
E826149
|
entity |
| Predicate | berätÜber |
P173974
|
FINISHED |
| Object | theologische Grundfragen der Landeskirche |
—
|
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: theologische Grundfragen der Landeskirche | Statement: [Landessynode, berätÜber, theologische Grundfragen der Landeskirche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: berätÜber Context triple: [Landessynode, berätÜber, theologische Grundfragen der Landeskirche]
-
A.
saidAbout
Indicates that a statement or assertion has been made concerning or in reference to a particular entity or subject.
-
B.
providesExpositionAbout
Indicates that one entity offers explanatory or background information clarifying or elaborating on another entity.
-
C.
providedInformationOn
Indicates that one entity supplied or communicated specific information or details to another entity.
-
D.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
E.
offersInformationOn
Indicates that one entity provides or makes available information about another entity or topic.
- 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_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. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:48 a.m.