Triple
T31209561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock of Cashel |
E795697
|
entity |
| Predicate | foundedAsEcclesiasticalSite |
P168043
|
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: [Rock of Cashel, foundedAsEcclesiasticalSite, 12th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsEcclesiasticalSite Context triple: [Rock of Cashel, foundedAsEcclesiasticalSite, 12th century]
-
A.
foundedAsChristianCathedral
Indicates that an institution or building was originally established as a Christian cathedral.
-
B.
foundedAsReligiousSiteInCentury
chosen
Indicates that something was originally established as a religious site during a specified century.
-
C.
foundingLocationOfChurch
Indicates the place where a particular church was originally founded or established.
-
D.
foundedOnSiteOf
Indicates that something was established or built at the same physical location where another, earlier entity or structure previously existed.
-
E.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 29, 2026, 9:09 p.m.