Triple
T859584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diwali |
E18568
|
entity |
| Predicate | modernTrend |
P8269
|
FINISHED |
| Object | promotion of eco-friendly celebrations |
—
|
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: promotion of eco-friendly celebrations | Statement: [Diwali, modernTrend, promotion of eco-friendly celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernTrend Context triple: [Diwali, modernTrend, promotion of eco-friendly celebrations]
-
A.
modernUse
Indicates how something is currently used or applied in modern times.
-
B.
contemporary
Indicates that two entities exist, occur, or are active during the same time period or historical era.
-
C.
modernPractice
chosen
Indicates that an entity engages in or reflects a contemporary, up-to-date way of doing something, following current methods, standards, or trends.
-
D.
modernization
Indicates a process by which something is updated, reformed, or transformed to align with contemporary standards, technologies, or practices.
-
E.
modernizationFeatures
Indicates that something includes characteristics, elements, or improvements associated with making it more modern or up to date.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac50e5ec81908ac0c4b7123b4ebb |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.