Triple
T15738073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wechselburg |
E381527
|
entity |
| Predicate | religiousTraditionAtMonastery |
P99929
|
FINISHED |
| Object | Benedictine |
—
|
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: Benedictine | Statement: [Wechselburg, religiousTraditionAtMonastery, Benedictine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousTraditionAtMonastery Context triple: [Wechselburg, religiousTraditionAtMonastery, Benedictine]
-
A.
monasticTradition
Indicates that an entity follows, belongs to, or is characterized by a particular monastic rule, lineage, or way of religious life.
-
B.
monasteryOrder
chosen
Indicates that a monastery belongs to, follows, or is affiliated with a particular religious order.
-
C.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
-
D.
monasteryAffiliation
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
-
E.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.