Triple
T29603913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organic Law 6/2006 |
E754524
|
entity |
| Predicate | dateOfSanction |
P166749
|
FINISHED |
| Object | 19 July 2006 |
—
|
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: 19 July 2006 | Statement: [Organic Law 6/2006, dateOfSanction, 19 July 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfSanction Context triple: [Organic Law 6/2006, dateOfSanction, 19 July 2006]
-
A.
fechaDeSanción
chosen
Indicates the date on which something (such as a law, regulation, or sanction) is formally enacted or approved.
-
B.
coSanctionedSince
Indicates that two or more entities have jointly imposed or been subject to a sanction starting from a specified point in time and continuing thereafter.
-
C.
sanctionYear
Indicates the year in which a sanction was imposed, enacted, or came into effect.
-
D.
dateOfDisqualification
Indicates the specific date on which an entity was formally disqualified from a role, status, competition, or eligibility.
-
E.
coSanctioningStartYear
Indicates the year in which a joint or collaborative sanctioning action officially began.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 28, 2026, 6:24 p.m.