Triple
T4617093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union medical device regulations |
E100892
|
entity |
| Predicate | MDRDateOfApplication |
P30
|
FINISHED |
| Object | 26 May 2021 |
—
|
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: 26 May 2021 | Statement: [European Union medical device regulations, MDRDateOfApplication, 26 May 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MDRDateOfApplication Context triple: [European Union medical device regulations, MDRDateOfApplication, 26 May 2021]
-
A.
dateOfSubmission
chosen
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
-
B.
admissionDate
Indicates the date on which an entity (such as a person, application, or item) is formally admitted, accepted, or entered into a system or institution.
-
C.
dateGranted
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
-
D.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
-
E.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e098c08190b769e76937dff700 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.