Triple
T32964863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bildungs- und Diakoniearbeit der Landeskirche |
E843340
|
entity |
| Predicate | wirdFinanziertDurch |
P67
|
FINISHED |
| Object | Kirchensteuern |
—
|
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: Kirchensteuern | Statement: [Bildungs- und Diakoniearbeit der Landeskirche, wirdFinanziertDurch, Kirchensteuern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wirdFinanziertDurch Context triple: [Bildungs- und Diakoniearbeit der Landeskirche, wirdFinanziertDurch, Kirchensteuern]
-
A.
fundedBy
chosen
Indicates that an entity receives financial support or resources from another entity.
-
B.
fundFinancedBy
Indicates that a particular fund receives its financial resources or backing from a specified source or entity.
-
C.
funderOf
Indicates that one entity provides financial support or funding for another entity, project, or activity.
-
D.
fundedEntityType
Indicates the type or category of entity that receives funding in the described funding relationship.
-
E.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1a02b5881908dcf3c96a1e6d800 |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.