Triple
T22664451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capital Markets Union |
E559745
|
entity |
| Predicate | formalActionPlanAdoptedOn |
P3399
|
FINISHED |
| Object | 30 September 2015 |
—
|
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: 30 September 2015 | Statement: [Capital Markets Union, formalActionPlanAdoptedOn, 30 September 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalActionPlanAdoptedOn Context triple: [Capital Markets Union, formalActionPlanAdoptedOn, 30 September 2015]
-
A.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
B.
implementedPlan
Indicates that a specific plan has been carried out or put into effect by an entity.
-
C.
decisionAdoptedAt
Indicates that a decision was formally adopted or approved at a specific time or event.
-
D.
formalizedAt
Indicates the point in time or event at which something is officially established, documented, or given formal status.
-
E.
dateAdopted
chosen
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f176617ed8819095a58a2c9f1e3918 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:08 p.m.