Triple
T21158308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domgemeinde St. Petrus Osnabrück |
E521367
|
entity |
| Predicate | parishTerritory |
P38128
|
FINISHED |
| Object | Bereich um den Osnabrücker Dom |
—
|
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: Bereich um den Osnabrücker Dom | Statement: [Domgemeinde St. Petrus Osnabrück, parishTerritory, Bereich um den Osnabrücker Dom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parishTerritory Context triple: [Domgemeinde St. Petrus Osnabrück, parishTerritory, Bereich um den Osnabrücker Dom]
-
A.
civilParishArea
Indicates the total geographic area encompassed by a given civil parish.
-
B.
parishIncludes
chosen
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
-
C.
parish
Indicates that an entity is administratively or ecclesiastically associated with a particular parish.
-
D.
civilParishIn
Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
-
E.
ecclesiasticalTerritory
Indicates that one entity is an ecclesiastical (church-governed) jurisdiction or territory associated with another entity, such as a religious organization or authority.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252dc3f0819094c6acf52a9f308d |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:59 p.m.