Triple
T33926182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stiftsstraße Stuttgart |
E869757
|
entity |
| Predicate | hasParishOfficeAddressFor |
P199934
|
FINISHED |
| Object | Evangelische Stiftskirchengemeinde Stuttgart |
—
|
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: Evangelische Stiftskirchengemeinde Stuttgart | Statement: [Stiftsstraße Stuttgart, hasParishOfficeAddressFor, Evangelische Stiftskirchengemeinde Stuttgart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishOfficeAddressFor Context triple: [Stiftsstraße Stuttgart, hasParishOfficeAddressFor, Evangelische Stiftskirchengemeinde Stuttgart]
-
A.
hasParishHouse
Indicates that a church or parish entity possesses or is associated with a specific parish house building.
-
B.
isInParishSeat
Indicates that an entity is located within the administrative center (parish seat) of a given parish.
-
C.
mainParishOf
Indicates that one parish serves as the primary or central parish associated with a given entity or area.
-
D.
hasParishOrganisation
Indicates that an entity is associated with or administered by a specific parish-level organizational unit.
-
E.
hasDistrictOfficeLocation
Indicates that an entity’s district office is located at a specified place or address.
- F. None of above. chosen
Provenance (4 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_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
| PDg | Predicate description generation | batch_69ff64b864f481909fcefc2b08595c89 |
completed | May 9, 2026, 4:45 p.m. |
Created at: May 1, 2026, 1:49 a.m.