Triple
T28174293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 United Kingdom European Union membership referendum |
E715546
|
entity |
| Predicate | triggeredProcess |
P55105
|
FINISHED |
| Object | Brexit |
—
|
NE NERFINISHED |
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 | Statement: [2016 United Kingdom European Union membership referendum, triggeredProcess, Brexit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggeredProcess Context triple: [2016 United Kingdom European Union membership referendum, triggeredProcess, Brexit]
-
A.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
triggeredResponse
Indicates that one entity’s action or event causes another entity to produce a specific reaction or output.
-
C.
triggeredFrom
chosen
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
-
D.
dynamicProcess
Indicates an ongoing, evolving sequence of changes or interactions that unfold over time rather than a fixed or static state.
-
E.
createdProcess
Indicates that an entity is responsible for originating or bringing into existence a particular process.
- 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_69efd6b340f0819095680e15dcdc1830 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6423929c8819099c32e0a42b0cd4e |
completed | May 2, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:15 p.m.