Triple
T24009487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Diarmaid |
E594486
|
entity |
| Predicate | hasSiteDedicatedTo |
P154849
|
FINISHED |
| Object | monastic ruins on Inchcleraun Island |
—
|
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: monastic ruins on Inchcleraun Island | Statement: [Saint Diarmaid, hasSiteDedicatedTo, monastic ruins on Inchcleraun Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiteDedicatedTo Context triple: [Saint Diarmaid, hasSiteDedicatedTo, monastic ruins on Inchcleraun Island]
-
A.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
B.
hasSiteStatus
Indicates the current operational or condition status assigned to a particular site.
-
C.
hasDedicatedStations
Indicates that specific stations are exclusively assigned or reserved for a particular entity or purpose.
-
D.
hasMainSite
Indicates that one entity is designated as the primary or central site associated with another entity.
-
E.
selectedAsSiteFor
Indicates that one entity has been chosen or designated to serve as the location or venue for another entity or activity.
- F. None of above. chosen
Provenance (4 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d46c77f88190806e6287e55c9136 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:41 p.m.