Triple
T33744160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cistercian Ten Duinen Abbey ruins |
E864653
|
entity |
| Predicate | foundedAsMonasteryInCentury |
P171021
|
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: [Cistercian Ten Duinen Abbey ruins, foundedAsMonasteryInCentury, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsMonasteryInCentury Context triple: [Cistercian Ten Duinen Abbey ruins, foundedAsMonasteryInCentury, 12th century]
-
A.
monasteryEstablished
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
-
B.
wasMonasticCentreFromCentury
chosen
Indicates that a place functioned as a monastic center starting from a specified century.
-
C.
monasticTraditionFoundedInYear
Indicates that a particular monastic tradition was established or came into existence in a specified year.
-
D.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
-
E.
numberOfMonasteriesFounded
Indicates the total count of monasteries that a given entity has established or founded.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: May 1, 2026, 1:44 a.m.