Triple
T22404604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regulation (EU) 2019/6 |
E553847
|
entity |
| Predicate | relevanceDate |
P148029
|
FINISHED |
| Object | 2022-01-28 |
—
|
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: 2022-01-28 | Statement: [Regulation (EU) 2019/6, relevanceDate, 2022-01-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relevanceDate Context triple: [Regulation (EU) 2019/6, relevanceDate, 2022-01-28]
-
A.
retrievalDate
Indicates the date on which an item, record, or resource was accessed, obtained, or retrieved.
-
B.
concernsDate
Indicates that something is related or refers specifically to a particular date or point in time.
-
C.
priorityDate
Indicates the date on which something is assigned or attains its priority status relative to other items or actions.
-
D.
titleDate
Indicates the date associated with a title, such as when it was granted, recorded, or became effective.
-
E.
dateOfRelatedEvent
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
- F. None of above. chosen
Provenance (4 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b6762c8190991fc14c5ca8e609 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.