Triple
T32218682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kremsmünster |
E823001
|
entity |
| Predicate | hasMonasticComplexFeature |
P196290
|
FINISHED |
| Object | church |
—
|
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: church | Statement: [Kremsmünster, hasMonasticComplexFeature, church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticComplexFeature Context triple: [Kremsmünster, hasMonasticComplexFeature, church]
-
A.
containsMonastery
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
-
B.
hasMonasticEnclosure
Indicates that an entity includes or is associated with a defined monastic enclosure area, typically separating monastic space from the outside or secular surroundings.
-
C.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
D.
hasNearbyMonastery
Indicates that one entity is located close to or in the vicinity of a monastery.
-
E.
hasMonasticCommunities
Indicates that an entity possesses, hosts, or is associated with one or more monastic communities.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69fe1fd58ad8819093d3d705e8521014 |
completed | May 8, 2026, 5:39 p.m. |
Created at: May 1, 2026, 12:38 a.m.