Triple
T17939356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kartik Krishna Paksha |
E448546
|
entity |
| Predicate | basisOfReckoning |
P64521
|
FINISHED |
| Object | lunar tithi (lunar day) |
—
|
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: lunar tithi (lunar day) | Statement: [Kartik Krishna Paksha, basisOfReckoning, lunar tithi (lunar day)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisOfReckoning Context triple: [Kartik Krishna Paksha, basisOfReckoning, lunar tithi (lunar day)]
-
A.
basingConcept
chosen
Indicates that one concept serves as the foundational basis or underlying rationale for another concept.
-
B.
basedInUniverseOn
Indicates that something is set or takes place within a fictional universe that is derived from, inspired by, or adapted from another source.
-
C.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
-
D.
bearingProvidedBy
Indicates that one entity supplies or furnishes a bearing (as a mechanical support component) for another entity.
-
E.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9533688190bff773c183ed8505 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.