Triple
T33489397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directive 2013/37/EU |
E857697
|
entity |
| Predicate | implementationDeadlineForMemberStates |
P8546
|
FINISHED |
| Object | 2015-07-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: 2015-07-18 | Statement: [Directive 2013/37/EU, implementationDeadlineForMemberStates, 2015-07-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementationDeadlineForMemberStates Context triple: [Directive 2013/37/EU, implementationDeadlineForMemberStates, 2015-07-18]
-
A.
hasDeadline
chosen
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
B.
postDeadlineRule
Indicates a rule or policy that applies to actions or conditions occurring after a specified deadline has passed.
-
C.
ratificationDeadlineExtendedTo
Indicates that the deadline by which a ratification must occur has been extended to a specified later date.
-
D.
apportionmentDataDeadlineOriginal
Indicates the original deadline by which apportionment-related data must be provided or finalized.
-
E.
implementationPeriod
Indicates the time span during which a plan, project, or agreement is actively carried out or executed.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:38 a.m.