Triple
T31600123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plano Verão |
E806327
|
entity |
| Predicate | implementedOnDate |
P90584
|
FINISHED |
| Object | 1989-01-15 |
—
|
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: 1989-01-15 | Statement: [Plano Verão, implementedOnDate, 1989-01-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedOnDate Context triple: [Plano Verão, implementedOnDate, 1989-01-15]
-
A.
implementedOn
Indicates that something (such as a feature, standard, or specification) is realized, executed, or put into effect within or on a particular platform, system, or environment.
-
B.
dateImplemented
chosen
Indicates the date on which something (such as a plan, rule, feature, or system) was put into effect or made operational.
-
C.
implementedProgramStartDate
Indicates the date on which a particular program was put into effect or began operating in practice.
-
D.
achievedOn
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
E.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:32 p.m.