Triple
T13768809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annaghdown |
E330820
|
entity |
| Predicate | dioceseHistory |
P94075
|
FINISHED |
| Object | former episcopal see |
—
|
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: former episcopal see | Statement: [Annaghdown, dioceseHistory, former episcopal see]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dioceseHistory Context triple: [Annaghdown, dioceseHistory, former episcopal see]
-
A.
hasDioceseHistory
Indicates that an entity has an associated historical record or account of its diocese, including its past developments, changes, or events.
-
B.
dioceseEstablishedBy
Indicates that a diocese was founded, created, or formally instituted by a particular person or authority.
-
C.
dioceseGovernedStart
Indicates the point in time when a particular authority or leader began governing a specific diocese.
-
D.
isHistoricDiocese
chosen
Indicates that an entity functioned as a diocese in the past but no longer exists as an active ecclesiastical jurisdiction.
-
E.
dioceseEstablishedBefore
Indicates that one diocese was formally established at an earlier date than another diocese.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0233ecc48190b934f085d2501eb1 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.