Triple
T18057146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B Specials |
E432066
|
entity |
| Predicate | allegedBias |
P47259
|
FINISHED |
| Object | pro-unionist |
—
|
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: pro-unionist | Statement: [B Specials, allegedBias, pro-unionist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedBias Context triple: [B Specials, allegedBias, pro-unionist]
-
A.
bias
chosen
Indicates a systematic preference or prejudice in favor of or against an entity, affecting how it is treated, evaluated, or represented relative to others.
-
B.
allegedBelligerent
Indicates that one entity is claimed or accused of being a hostile or warring party in relation to another entity or conflict.
-
C.
allegedGoal
Indicates that one entity is claimed or reported to have the goal or intended objective of another entity, without asserting that the goal is actually true.
-
D.
allegedByOpponents
Indicates that a claim or accusation is made by opponents of the subject.
-
E.
allegedInconsistencyWith
Indicates a claimed or suspected contradiction or mismatch between one thing and another.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c103cedc819086a905269b118795 |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:26 a.m.