Triple
T33926175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stiftsstraße Stuttgart |
E869757
|
entity |
| Predicate | hasParishOfficeOf |
P42007
|
FINISHED |
| Object | Stiftskirche 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: Stiftskirche Stuttgart | Statement: [Stiftsstraße Stuttgart, hasParishOfficeOf, Stiftskirche Stuttgart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParishOfficeOf Context triple: [Stiftsstraße Stuttgart, hasParishOfficeOf, Stiftskirche Stuttgart]
-
A.
hasParishFunction
Indicates that an entity performs, fulfills, or is assigned a specific functional role within a parish.
-
B.
hasParishOrganisation
Indicates that an entity is associated with or administered by a specific parish-level organizational unit.
-
C.
isParishSeatOf
chosen
Indicates that a location serves as the administrative center or main seat of government for a particular parish.
-
D.
hasParishHouse
Indicates that a church or parish entity possesses or is associated with a specific parish house building.
-
E.
hasParishGovernmentSeat
Indicates that a parish serves as the administrative or governmental seat for a specified jurisdiction or governing body.
- 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_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: May 1, 2026, 1:49 a.m.