Triple
T20852690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markets in Financial Instruments Directive II |
E513402
|
entity |
| Predicate | enteredIntoApplication |
P142105
|
FINISHED |
| Object | 2018-01-03 |
—
|
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: 2018-01-03 | Statement: [Markets in Financial Instruments Directive II, enteredIntoApplication, 2018-01-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredIntoApplication Context triple: [Markets in Financial Instruments Directive II, enteredIntoApplication, 2018-01-03]
-
A.
enteredIntoBy
Indicates that an agreement, contract, or formal arrangement has been initiated or established by a particular party.
-
B.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
C.
enteredIntoForce
Indicates that a law, treaty, agreement, or regulation has become legally effective and binding from a specific point in time.
-
D.
enteredARL
Indicates that an entity has gone into or gained access to an ARL (a specific location, area, or restricted zone).
-
E.
enteredAdministration
Indicates that an entity has formally begun serving in an administrative role or office within an organization or institution.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a4df5c8190aa0e7684ad6fc9f2 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:44 p.m.