Triple
T31291674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glendalough |
E797957
|
entity |
| Predicate | timePeriodOfMonasticFoundation |
P53542
|
FINISHED |
| Object | 6th 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: 6th century | Statement: [Glendalough, timePeriodOfMonasticFoundation, 6th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfMonasticFoundation Context triple: [Glendalough, timePeriodOfMonasticFoundation, 6th century]
-
A.
monasticTraditionFoundedInYear
Indicates that a particular monastic tradition was established or came into existence in a specified year.
-
B.
historicalEraOfMonastery
chosen
Indicates the historical era or period during which the monastery was founded, active, or most prominently associated.
-
C.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
-
D.
numberOfMonasteriesFounded
Indicates the total count of monasteries that a given entity has established or founded.
-
E.
wasMonasticCentreFromCentury
Indicates that a place functioned as a monastic center starting from a specified century.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 29, 2026, 9:14 p.m.