Triple
T31209565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock of Cashel |
E795697
|
entity |
| Predicate | cathedralConstructionEnd |
P30041
|
FINISHED |
| Object | 15th 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: 15th century | Statement: [Rock of Cashel, cathedralConstructionEnd, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cathedralConstructionEnd Context triple: [Rock of Cashel, cathedralConstructionEnd, 15th century]
-
A.
cathedralConstructionStarted
Indicates that the process of constructing a cathedral has begun.
-
B.
cathedralPeriodEnd
Indicates the time or date when a cathedral’s associated historical or architectural period comes to an end.
-
C.
hasCathedralCompletedIn
chosen
Indicates that a cathedral associated with an entity was completed in a specified year or time period.
-
D.
cathedralSince
Indicates that an entity has held the status or function of a cathedral continuously from a specified point in time onward.
-
E.
cathedral
Indicates that an entity is a cathedral, i.e., it has the status or function of a principal church, typically one that is the seat of a bishop.
- 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_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:09 p.m.