Triple
T6535196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenery Day |
E152341
|
entity |
| Predicate | dateChangeEffectiveYear |
P23631
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Greenery Day, dateChangeEffectiveYear, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateChangeEffectiveYear Context triple: [Greenery Day, dateChangeEffectiveYear, 2007]
-
A.
movedToCurrentDateYear
Indicates that an entity has been moved, updated, or adjusted so that its associated date now falls within the current calendar year.
-
B.
effectiveYear
chosen
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
C.
dateChangesWith
Indicates that the date associated with one entity is altered or updated in conjunction with, or as a result of, a change involving another entity.
-
D.
startDateChangedTo
Indicates that the start date of something has been modified from its previous value to a new specified date.
-
E.
yearTurned
Indicates the specific year in which an entity changed state, status, or classification (e.g., when it became, reached, or turned into something).
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6adc05da88190b402085954cec8e0 |
completed | March 27, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69c68abd9c7c819099e4fe8097cd1b28 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:46 p.m.