Triple
T24570278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballylooby-Castlegrace area |
E607917
|
entity |
| Predicate | alsoWithin |
P57262
|
FINISHED |
| Object | Roman Catholic Diocese of Waterford and Lismore |
—
|
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: Roman Catholic Diocese of Waterford and Lismore | Statement: [Ballylooby-Castlegrace area, alsoWithin, Roman Catholic Diocese of Waterford and Lismore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoWithin Context triple: [Ballylooby-Castlegrace area, alsoWithin, Roman Catholic Diocese of Waterford and Lismore]
-
A.
existsWithin
chosen
Indicates that one entity is located inside the spatial, temporal, or conceptual boundaries of another entity.
-
B.
alsoIn
Indicates that an entity participates in or belongs to an additional context, group, or location alongside another already specified one.
-
C.
accessibleWithin
Indicates that one entity can be reached, used, or entered from within the spatial or contextual bounds of another entity.
-
D.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
E.
alsoMetAt
Indicates that the same entities met together at an additional, distinct place or event beyond a previously mentioned meeting location.
- 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_69e2c4cdab6c8190aae6e5d3de55c95e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a92468c881908f79de0ea43b2bb8 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:28 a.m.