Triple
T35332445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rama Ekadashi |
E1020357
|
entity |
| Predicate | breakingFast |
P183029
|
FINISHED |
| Object | Dwadashi (twelfth lunar day) morning |
—
|
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: Dwadashi (twelfth lunar day) morning | Statement: [Rama Ekadashi, breakingFast, Dwadashi (twelfth lunar day) morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakingFast Context triple: [Rama Ekadashi, breakingFast, Dwadashi (twelfth lunar day) morning]
-
A.
budbreak
Indicates the point in time or condition under which buds on a plant begin to open and resume active growth.
-
B.
break
Indicates that one entity causes another entity to separate into pieces, stop functioning, or otherwise lose its normal integrity or continuity.
-
C.
brokenBy
Indicates that one entity causes the damage, destruction, or loss of functionality of another entity.
-
D.
brokenIn
Indicates that an object or system has become nonfunctional or damaged while located within or inside a particular place, context, or container.
-
E.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.