Triple
T25391202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermanagh |
E636169
|
entity |
| Predicate | hasCouncilAreaSuccessor |
P113011
|
FINISHED |
| Object | Fermanagh and Omagh district |
—
|
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: Fermanagh and Omagh district | Statement: [Fermanagh, hasCouncilAreaSuccessor, Fermanagh and Omagh district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCouncilAreaSuccessor Context triple: [Fermanagh, hasCouncilAreaSuccessor, Fermanagh and Omagh district]
-
A.
hasCouncilAreaName
Indicates that an entity is associated with a council area identified by a specific name.
-
B.
hasCountySeatSuccessor
Indicates that one county seat has been succeeded or replaced by another as the official administrative center for a county.
-
C.
hasCouncilAreaStatusFrom
Indicates that an entity holds council area status starting from a specified point in time.
-
D.
successorTerritorialEntity
Indicates that one territorial entity directly follows and replaces another in governing authority or jurisdiction over a given area.
-
E.
succeededByCouncilArea
chosen
Indicates that one council area is replaced or followed in administrative succession by another council area.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 21, 2026, 1:49 p.m.