Triple
T242578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let's Move! |
E4963
|
entity |
| Predicate | endOfActivePromotion |
P140
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Let's Move!, endOfActivePromotion, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfActivePromotion Context triple: [Let's Move!, endOfActivePromotion, 2017]
-
A.
redeemabilityEndedUnder
Indicates that the period or conditions under which something could be redeemed have come to an end under a specified context, rule, or authority.
-
B.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
-
C.
redeemabilityEndedReason
Indicates the reason why the ability to redeem something (e.g., a product, offer, or asset) has ended.
-
D.
productionEnd
Indicates that a production process, activity, or run has come to its completion or final stopping point.
-
E.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69a257c3d0708190b0871c4269d273e6 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b60ad308190b12f119960a8bde7 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.