Triple
T10786262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jitiya |
E254458
|
entity |
| Predicate | occursInLunarPhase |
P20188
|
FINISHED |
| Object | Krishna Paksha |
—
|
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: Krishna Paksha | Statement: [Jitiya, occursInLunarPhase, Krishna Paksha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInLunarPhase Context triple: [Jitiya, occursInLunarPhase, Krishna Paksha]
-
A.
astronomicalPhase
Indicates the specific stage or phase an astronomical object (such as a planet or moon) is in within its cyclical progression as observed over time.
-
B.
isOnlyLargeMoonWith
Indicates that one moon is the sole large moon possessing a specified feature, property, or relationship among all moons in consideration.
-
C.
hasLunarBasis
Indicates that something is founded on, derived from, or fundamentally based on the Moon or lunar characteristics.
-
D.
isLunisolar
Indicates that something is based on or determined by both the cycles of the moon and the sun.
-
E.
lunarCalendar
chosen
Indicates that the referenced system, event, or date is defined, measured, or scheduled according to a calendar based on the phases or cycles of the Moon.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d44b488190a9f3ab9b177e737a |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.