Triple
T3110462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chhath Puja |
E64936
|
entity |
| Predicate | secondDayName |
P45999
|
FINISHED |
| Object | Kharna |
—
|
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: Kharna | Statement: [Chhath Puja, secondDayName, Kharna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondDayName Context triple: [Chhath Puja, secondDayName, Kharna]
-
A.
dayName
Indicates the specific name of the day of the week associated with a given date or time.
-
B.
secondLetter
Indicates that one entity is the second letter (in sequence or position) of another entity, typically a string or word.
-
C.
secondWord
Indicates that one entity is the second word in sequence immediately following the first entity in a text or utterance.
-
D.
secondGenerationName
Indicates that the object is the name given to the second generation derived from the subject.
-
E.
secondTestName
Indicates that an entity serves as the second named test or secondary test designation associated with another entity.
- F. None of above. chosen
Provenance (4 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada437c5e08190af22f6fa11cf9252 |
completed | March 8, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:04 p.m.