Triple
T33926485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grundsätze der kirchlichen Diakonie |
E869764
|
entity |
| Predicate | verwendetBegriff |
P16497
|
FINISHED |
| Object | diakonischer Dienst |
—
|
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: diakonischer Dienst | Statement: [Grundsätze der kirchlichen Diakonie, verwendetBegriff, diakonischer Dienst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verwendetBegriff Context triple: [Grundsätze der kirchlichen Diakonie, verwendetBegriff, diakonischer Dienst]
-
A.
usedTerm
chosen
Indicates that one entity employed, referenced, or applied a particular term in some context.
-
B.
useOfTerm
Indicates that one entity employs or applies a specific term or expression in reference to another entity or context.
-
C.
isFamouslyUsedIn
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
D.
используетсяС
Indicates that something is used together with or by means of another entity.
-
E.
termAlsoUsedFor
Indicates that one term is also used to refer to the same or closely related concept as another term.
- 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.