Triple
T18750514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directive 98/79/EC on in vitro diagnostic medical devices |
E458511
|
entity |
| Predicate | applicationDate |
P120539
|
FINISHED |
| Object | 2003-12-07 |
—
|
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: 2003-12-07 | Statement: [Directive 98/79/EC on in vitro diagnostic medical devices, applicationDate, 2003-12-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationDate Context triple: [Directive 98/79/EC on in vitro diagnostic medical devices, applicationDate, 2003-12-07]
-
A.
appliedDate
chosen
Indicates the date on which an application or request was submitted or made.
-
B.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
-
C.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
entryDate
Indicates the date on which an entity was first recorded, created, or entered into a system or context.
-
E.
associatedWorkDate
Indicates the date on which a related or associated work (such as a publication, performance, or creation) is linked to the subject entity.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ec71cc8190bb6d3fa6cca6dc8c |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.