Triple
T33926206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelisches Kirchenrecht |
E869758
|
entity |
| Predicate | TeilgebietVon |
P111186
|
FINISHED |
| Object | deutsches Staatskirchenrecht |
—
|
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: deutsches Staatskirchenrecht | Statement: [Evangelisches Kirchenrecht, TeilgebietVon, deutsches Staatskirchenrecht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TeilgebietVon Context triple: [Evangelisches Kirchenrecht, TeilgebietVon, deutsches Staatskirchenrecht]
-
A.
subArea
chosen
Indicates that one area is a constituent or contained part of a larger area.
-
B.
subregionOfFieldwork
Indicates that one fieldwork area is a smaller, contained subregion within another, larger fieldwork area.
-
C.
collectionSubdivision
Indicates that one collection is a constituent part, section, or subdivision of a larger collection.
-
D.
partOfCountrySubdivision
Indicates that one geographic or administrative unit is contained within and forms a component part of a larger country subdivision.
-
E.
categorySubdivision
Indicates that one category functions as a subdivision or subcategory within another broader category.
- 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_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.