Triple
T19281596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panchami |
E482200
|
entity |
| Predicate | hasPositionInPaksha |
P135434
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Panchami, hasPositionInPaksha, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionInPaksha Context triple: [Panchami, hasPositionInPaksha, 5]
-
A.
positionInSaptarishi
Indicates the specific place or ordering that an entity occupies within the Saptarishi group.
-
B.
occursOnNakshatra
Indicates that an event or phenomenon takes place during, or is associated with, a specific nakshatra (lunar mansion) in the traditional Indian astronomical/astrological system.
-
C.
hasNumberOfTithis
Indicates the relationship that specifies how many tithis (lunar days) are associated with a given entity or period.
-
D.
hasPositionInMahabharata
Indicates that one entity holds or is assigned a specific role, rank, or position within the context of the Mahabharata narrative.
-
E.
positionInDasamGranth
Indicates the specific location or ordering of a referenced element within the text of the Dasam Granth.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbff1e6c819094ae6a5ad40adb65 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:30 p.m.