Triple
T19447154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Causeway Coast and Glens district |
E486507
|
entity |
| Predicate | firstElectionsHeld |
P8672
|
FINISHED |
| Object | 2014-05-22 |
—
|
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: 2014-05-22 | Statement: [Causeway Coast and Glens district, firstElectionsHeld, 2014-05-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstElectionsHeld Context triple: [Causeway Coast and Glens district, firstElectionsHeld, 2014-05-22]
-
A.
firstElectionHeldIn
Indicates the location where an entity’s first election was conducted.
-
B.
firstConstitutionalElectionsHeld
Indicates that the first elections conducted under a new or newly adopted constitution have taken place.
-
C.
firstElectionDate
chosen
Indicates the date on which an entity (such as a person or office) participated in or held its first election.
-
D.
firstElectionUnder
Indicates that an election was the first one conducted under a particular rule, system, constitution, or governing framework.
-
E.
firstElectionYear
Indicates the calendar year in which an entity (such as a person, office, or political body) first participated in or was subject to an election.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338b25d88190bc137a411576c73f |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.