Triple
T31200437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aghaboe |
E795456
|
entity |
| Predicate | wasMonasticCentreUntilCentury |
P156533
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Aghaboe, wasMonasticCentreUntilCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMonasticCentreUntilCentury Context triple: [Aghaboe, wasMonasticCentreUntilCentury, 16th century]
-
A.
wasMonasticCentreFromCentury
Indicates that a place functioned as a monastic center starting from a specified century.
-
B.
wasEcclesiasticalCentreUntilCentury
chosen
Indicates that a place functioned as an ecclesiastical (church or religious) center up to, but not beyond, a specified century.
-
C.
monasteryAbandonedByCentury
Indicates that a monastery had been abandoned and was no longer in use by a specified century.
-
D.
monasticTraditionFoundedInYear
Indicates that a particular monastic tradition was established or came into existence in a specified year.
-
E.
monasteryEstablished
Indicates that a monastery was founded or formally established at a particular time, place, or by a specific agent.
- 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_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:09 p.m.