Triple
T6574753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anant Chaturdashi |
E155530
|
entity |
| Predicate | hasSacredThreadColor |
P31069
|
FINISHED |
| Object | saffron and red for men |
—
|
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: saffron and red for men | Statement: [Anant Chaturdashi, hasSacredThreadColor, saffron and red for men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredThreadColor Context triple: [Anant Chaturdashi, hasSacredThreadColor, saffron and red for men]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
hasLiturgicalColor
Indicates that something is associated with a specific liturgical color used in religious rites or ceremonies.
-
C.
hasPhysicalFeature
Indicates that one entity possesses or exhibits a specific physical characteristic or feature of another entity.
-
D.
hasCaste
Indicates that an entity belongs to or is associated with a particular caste within a social or hierarchical system.
-
E.
hasTraditionalColors
chosen
Indicates that an entity is associated with colors that are traditionally or customarily linked to it.
- 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_69c688151254819080387f87deab8fa7 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:53 p.m.