Triple
T31056966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directive (EU) 2016/1148 |
E791421
|
entity |
| Predicate | ceasesToBeInForce |
P71730
|
FINISHED |
| Object | 2024-10-18 |
—
|
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: 2024-10-18 | Statement: [Directive (EU) 2016/1148, ceasesToBeInForce, 2024-10-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasesToBeInForce Context triple: [Directive (EU) 2016/1148, ceasesToBeInForce, 2024-10-18]
-
A.
cessationDate
Indicates the date on which an ongoing state, activity, or relationship comes to an end.
-
B.
legalStatusEnd
chosen
Indicates the point or event at which a previously valid legal status, condition, or arrangement ceases to be in effect.
-
C.
ceasedToApplyOn
Indicates that a rule, condition, or status stopped being valid or in effect starting from a specific point in time.
-
D.
neverCameIntoForce
Indicates that a proposed law, agreement, or regulation was formally created but never became legally effective or operational.
-
E.
repealEffectiveIn
Indicates that a repeal of a law, rule, or regulation becomes legally operative within a specified jurisdiction or context.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695441b3c8190943f67a89e070329 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9 p.m.