Triple
T1659505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Ireland Protocol |
E35872
|
entity |
| Predicate | fullyAppliedFrom |
P22780
|
FINISHED |
| Object | 2021-01-01 |
—
|
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: 2021-01-01 | Statement: [Northern Ireland Protocol, fullyAppliedFrom, 2021-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullyAppliedFrom Context triple: [Northern Ireland Protocol, fullyAppliedFrom, 2021-01-01]
-
A.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
B.
appliedBecauseOf
Indicates that one entity is applied, used, or enacted as a consequence or result of another specified cause or condition.
-
C.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
D.
appliesFrom
chosen
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
-
E.
appliedToStatesThrough
Indicates that something (such as a rule, policy, or process) is implemented or enforced by means of, or via the mediation of, particular states.
- 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.