Triple
T20602235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Abbey of Werden |
E506211
|
entity |
| Predicate | typeOfMonasticHouse |
P37070
|
FINISHED |
| Object | male monastery |
—
|
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: male monastery | Statement: [Imperial Abbey of Werden, typeOfMonasticHouse, male monastery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMonasticHouse Context triple: [Imperial Abbey of Werden, typeOfMonasticHouse, male monastery]
-
A.
monasteryType
chosen
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
-
B.
monasticResidence
Indicates that one entity serves as the place of residence for a monastic individual or community.
-
C.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
D.
monasteryOrder
Indicates that a monastery belongs to, follows, or is affiliated with a particular religious order.
-
E.
monasteryAffiliation
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa20f5c881909265ce7d96efc487 |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.