Triple
T8375760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union (Withdrawal Agreement) Act 2020 |
E197569
|
entity |
| Predicate | relatedToDate |
P57503
|
FINISHED |
| Object | 2020-01-31 |
—
|
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: 2020-01-31 | Statement: [European Union (Withdrawal Agreement) Act 2020, relatedToDate, 2020-01-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToDate Context triple: [European Union (Withdrawal Agreement) Act 2020, relatedToDate, 2020-01-31]
-
A.
linkedToDate
chosen
Indicates that an entity is associated or connected to a specific date or point in time.
-
B.
dateOfRelatedEvent
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
C.
dateRelativeTo
Indicates a temporal relationship where one date is defined, positioned, or interpreted in relation to another reference date (e.g., before, after, or offset by a specific duration).
-
D.
laterRelationWith
Indicates that one entity stands in a temporal relationship to another such that it occurs or exists at a later time than the other.
-
E.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80bf6b8081909b98762b1f900bef |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.