Triple
T20458116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irish border |
E501848
|
entity |
| Predicate | wasKeyIssueIn |
P29037
|
FINISHED |
| Object | Brexit negotiations |
—
|
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: Brexit negotiations | Statement: [Irish border, wasKeyIssueIn, Brexit negotiations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasKeyIssueIn Context triple: [Irish border, wasKeyIssueIn, Brexit negotiations]
-
A.
wasIssueAt
Indicates that a particular issue existed or occurred at a specific time, place, or contextual point.
-
B.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
C.
involvesIssue
chosen
Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
-
D.
hasKeyIssue
Indicates that an entity is associated with a primary or central problem, concern, or topic of importance.
-
E.
hadKeyIssue
Indicates that an entity experienced a primary or critical problem related to a key aspect, factor, or component.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a2a8a88190992211b09295d8ea |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.