Triple
T29408158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ley General de Educación de Uruguay |
E745825
|
entity |
| Predicate | fechaDePublicación |
P30105
|
FINISHED |
| Object | 2009-01-09 |
—
|
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: 2009-01-09 | Statement: [Ley General de Educación de Uruguay, fechaDePublicación, 2009-01-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fechaDePublicación Context triple: [Ley General de Educación de Uruguay, fechaDePublicación, 2009-01-09]
-
A.
finalPublicationDate
Indicates the date on which a work is officially and definitively published in its final form.
-
B.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
C.
isPublishedAt
Indicates that an item (such as a work, article, or resource) is made publicly available at or through a specific venue, platform, or location.
-
D.
hasPublicationDate
chosen
Indicates that an entity is associated with the specific date on which it was published.
-
E.
fullPublicationDate
Indicates the complete calendar date on which something is formally published, including day, month, and year.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a35eeb48190872f62f2e455ffee |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 2:55 p.m.