Triple
T26771660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Leighlin (historical) |
E675093
|
entity |
| Predicate | mergedTitleInto |
P88537
|
FINISHED |
| Object | Bishop of Kildare and Leighlin |
—
|
NE NERFINISHED |
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: Bishop of Kildare and Leighlin | Statement: [Diocese of Leighlin (historical), mergedTitleInto, Bishop of Kildare and Leighlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedTitleInto Context triple: [Diocese of Leighlin (historical), mergedTitleInto, Bishop of Kildare and Leighlin]
-
A.
editedTitle
Indicates that one entity has modified or changed the title of another entity.
-
B.
titleCombinesWith
chosen
Indicates that one title can be merged or used together with another title to form a combined or composite title.
-
C.
aggregateTitle
Indicates that one entity serves as a collective or overarching title that groups or summarizes multiple related items or works.
-
D.
mergedInto
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
E.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 4:02 a.m.