Triple
T24247898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eldena Abbey ruins |
E603432
|
entity |
| Predicate | foundedAsMonasteryIn |
P52045
|
FINISHED |
| Object | 12th century |
—
|
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: 12th century | Statement: [Eldena Abbey ruins, foundedAsMonasteryIn, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsMonasteryIn Context triple: [Eldena Abbey ruins, foundedAsMonasteryIn, 12th century]
-
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.
foundedAsConventFor
Indicates that an institution or building was originally established specifically to serve as a convent for a particular religious community or group.
-
D.
founderOfMonastery
Indicates that a person established or founded a particular monastery.
-
E.
refoundedAsBenedictineMonastery
Indicates that something was re-established or reorganized specifically as a Benedictine 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b860a0c81908c884ae876b46093 |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:04 a.m.