Triple
T25160500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Wiener Neustadt |
E626422
|
entity |
| Predicate | churchBuildingType |
P92816
|
FINISHED |
| Object | cathedral chapter |
—
|
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: cathedral chapter | Statement: [Diocese of Wiener Neustadt, churchBuildingType, cathedral chapter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchBuildingType Context triple: [Diocese of Wiener Neustadt, churchBuildingType, cathedral chapter]
-
A.
religiousBuildingInstanceOf
chosen
Indicates that a specific religious building is an instance of a particular class or type of religious building.
-
B.
religionBuildingDenomination
Indicates the specific religious denomination with which a religious building is affiliated or to which it belongs.
-
C.
inReligiousStructure
Indicates that one entity is located within or inside a building or structure used for religious purposes.
-
D.
formerReligiousBuilding
Indicates that a building previously served a religious function but no longer does so.
-
E.
cathedralChurch
Indicates that one church serves as the cathedral (principal church and episcopal seat) of another ecclesiastical jurisdiction or entity.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f46b8d45548190a5bdb4fba1d3ba4e |
completed | May 1, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:31 a.m.