Triple
T9464678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memleben |
E228239
|
entity |
| Predicate | foundingOfMonastery |
P52045
|
FINISHED |
| Object | circa 979 |
—
|
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: circa 979 | Statement: [Memleben, foundingOfMonastery, circa 979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundingOfMonastery Context triple: [Memleben, foundingOfMonastery, circa 979]
-
A.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
-
B.
monasteryEstablished
chosen
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
-
C.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
D.
refoundedAsBenedictineMonastery
Indicates that something was re-established or reorganized specifically as a Benedictine monastery.
-
E.
monasteryType
Indicates the specific kind or classification of a monastery in relation to its broader religious or organizational category.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fdad3c4819083b06f1b45acc85a |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.