Triple
T25414225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ardmore, County Waterford, Ireland |
E636784
|
entity |
| Predicate | monasticSiteDate |
P53542
|
FINISHED |
| Object | 5th 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: 5th century | Statement: [Ardmore, County Waterford, Ireland, monasticSiteDate, 5th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticSiteDate Context triple: [Ardmore, County Waterford, Ireland, monasticSiteDate, 5th century]
-
A.
monasteryEstablished
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
-
B.
monasticTraditionFoundedInYear
Indicates that a particular monastic tradition was established or came into existence in a specified year.
-
C.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
-
D.
monasticCenters
Indicates that one entity serves as a monastic center or hub for religious monastic life in relation to another entity.
-
E.
historicalEraOfMonastery
chosen
Indicates the historical era or period during which the monastery was founded, active, or most prominently associated.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b010c50881909a6b77af88dd0579 |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:55 p.m.