Triple
T22318647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belfast South |
E551718
|
entity |
| Predicate | hasVoterProfile |
P85910
|
FINISHED |
| Object | mixed unionist and nationalist support |
—
|
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: mixed unionist and nationalist support | Statement: [Belfast South, hasVoterProfile, mixed unionist and nationalist support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVoterProfile Context triple: [Belfast South, hasVoterProfile, mixed unionist and nationalist support]
-
A.
hasElectorateProfile
chosen
Indicates that an entity is associated with a specific electorate-related profile describing its voting or demographic characteristics.
-
B.
hasVoterRegister
Indicates that an entity maintains or possesses an official register or list of eligible voters.
-
C.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
-
D.
hasVoterRegistrationTendency
Indicates a tendency or likelihood for an entity to register (or be registered) as a voter.
-
E.
hasTypeOfVoters
Indicates that an entity is associated with or characterized by a particular category or kind of voters.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15762fac08190a6a514baffbbbca1 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.