Triple
T37366854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermanagh District Council |
E927733
|
entity |
| Predicate | boundaryChangeImplementedOn |
P21193
|
FINISHED |
| Object | 2015-04-01 |
—
|
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: 2015-04-01 | Statement: [Fermanagh District Council, boundaryChangeImplementedOn, 2015-04-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryChangeImplementedOn Context triple: [Fermanagh District Council, boundaryChangeImplementedOn, 2015-04-01]
-
A.
borderChange
chosen
Indicates a change in the boundaries between geographic or political entities, such as when borders are redrawn, expanded, reduced, or otherwise altered over time.
-
B.
hasBoundaryChangeOrigin
Indicates that a boundary change event originates from or is caused by a specified source or prior state.
-
C.
limitsOnChange
Indicates that there are constraints or restrictions placed on how much or in what ways something may be altered or modified.
-
D.
bondChange
Indicates a change in the type, order, or presence of a bond between two entities, such as forming, breaking, or altering a connection.
-
E.
namespaceChangedTo
Indicates that an entity’s namespace has been updated or reassigned from its previous value to a new one.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.