Triple
T31142550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ossory |
E793827
|
entity |
| Predicate | associatedMonasticSite |
P207364
|
FINISHED |
| Object | Aghaboe |
E795456
|
NE 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: Aghaboe | Statement: [Ossory, associatedMonasticSite, Aghaboe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMonasticSite Context triple: [Ossory, associatedMonasticSite, Aghaboe]
-
A.
monasticCenters
Indicates that one entity serves as a monastic center or hub for religious monastic life in relation to another entity.
-
B.
monasteriesAre
Indicates that a subject is classified as, functions as, or is identified with monasteries.
-
C.
monasteryDedicatedTo
Indicates that a monastery is formally devoted or consecrated to a particular deity, saint, religious figure, or sacred concept.
-
D.
monasteryAffiliation
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
-
E.
placeOfMonasticFoundation
Indicates the location where a monastic community or monastery was originally established or founded.
- F. None of above. chosen
Provenance (5 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a295903cbbc81909e02d6093acab5cc |
completed | June 10, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:06 p.m.