Triple
T27849908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evangelische Kirchengemeinde St. Marien – Friedrichswerder |
E703921
|
entity |
| Predicate | hasParishNamePart |
P115858
|
FINISHED |
| Object | St. Marien |
—
|
NE NERFINISHED |
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: St. Marien | Statement: [Evangelische Kirchengemeinde St. Marien – Friedrichswerder, hasParishNamePart, St. Marien]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishNamePart Context triple: [Evangelische Kirchengemeinde St. Marien – Friedrichswerder, hasParishNamePart, St. Marien]
-
A.
parishName
chosen
Indicates that an entity has the specified parish as its official or recorded name.
-
B.
hasCivilParishName
Indicates that an entity has a specific civil parish name as its designated official name at the civil parish level.
-
C.
parishWith
Indicates that one entity is associated with, belongs to, or is administered together with another entity as part of the same parish.
-
D.
mainParishOf
Indicates that one parish serves as the primary or central parish associated with a given entity or area.
-
E.
parishIncludes
Indicates that a parish geographically or administratively contains or encompasses another entity or area.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 27, 2026, 6:10 p.m.