Triple
T18412279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid Ulster |
E441787
|
entity |
| Predicate | hasRelativelyWeakVoteFor |
P131517
|
FINISHED |
| Object | unionist parties |
—
|
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: unionist parties | Statement: [Mid Ulster, hasRelativelyWeakVoteFor, unionist parties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativelyWeakVoteFor Context triple: [Mid Ulster, hasRelativelyWeakVoteFor, unionist parties]
-
A.
hasRelativeVotingPower
Indicates that one entity possesses a specified level or proportion of voting power relative to another entity or group.
-
B.
hasEqualVoteFor
Indicates that two or more entities possess the same voting power or weight in a given decision or context.
-
C.
votedWithMajorityIn
Indicates that an entity cast its vote in alignment with the majority decision within a given voting event or body.
-
D.
hasVotingPower
Indicates that an entity possesses the authority or capacity to participate in a decision-making or electoral process by casting votes.
-
E.
mayHaveCastingVote
Indicates that an entity is permitted to exercise a casting (tie-breaking) vote in a decision-making process.
- F. None of above. chosen
Provenance (4 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a24e130819082b92f98d8d5fa3c |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 10:47 a.m.