Triple
T25961138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaishakha |
E645539
|
entity |
| Predicate | moonPhaseStructure |
P159603
|
FINISHED |
| Object | Shukla Paksha and Krishna Paksha |
—
|
NE NERFINISHED |
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: Shukla Paksha and Krishna Paksha | Statement: [Vaishakha, moonPhaseStructure, Shukla Paksha and Krishna Paksha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moonPhaseStructure Context triple: [Vaishakha, moonPhaseStructure, Shukla Paksha and 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.
moonSightingRole
Indicates the specific role or capacity an entity has in the context of observing, reporting, or validating a moon sighting.
-
C.
associatedMoon
Indicates that one celestial body is the moon that is associated with, or orbits, another celestial body.
-
D.
largeMoon
Indicates that a moon has a size or diameter significantly greater than a typical or reference moon.
-
E.
hasLunarPhaseStart
Indicates that an entity (such as a lunar phase event) has a specific starting time or point at which that lunar phase begins.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604c60fe0819092ad09d1c5b0c100 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:47 a.m.