Triple
T20713440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribute Store (seasonal) |
E509104
|
entity |
| Predicate | decorChange |
P38144
|
FINISHED |
| Object | changes decor to match current event |
—
|
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: changes decor to match current event | Statement: [Tribute Store (seasonal), decorChange, changes decor to match current event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decorChange Context triple: [Tribute Store (seasonal), decorChange, changes decor to match current event]
-
A.
decorChanges
chosen
Indicates that an entity alters or updates the decorative appearance or arrangement of another entity or environment.
-
B.
decorChangedBy
Indicates that a change in decor or visual appearance was caused or brought about by a specific entity or action.
-
C.
modification
Indicates a change made to an existing entity, altering its properties, structure, or state from a prior version.
-
D.
changeDescription
Indicates that an entity’s descriptive information has been modified from a previous state.
-
E.
featureChange
Indicates a modification in the properties, characteristics, or attributes of an entity between two states or points in time.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d001788190a524a17347f9de67 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.