Triple
T17951372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashyapa |
E448838
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Bhasa |
—
|
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: Bhasa | Statement: [Kashyapa, spouse, Bhasa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhasa Context triple: [Kashyapa, spouse, Bhasa]
-
A.
Bhasa
chosen
Bhasa was an early and influential classical Sanskrit playwright, traditionally dated before Kalidasa, known for his innovative dramatic works rediscovered in the 20th century.
-
B.
Khotta Bhasha
Khotta Bhasha is an Indo-Aryan language variety spoken primarily in eastern India, closely related to and often considered a form of Khortha.
-
C.
Juang Bhasha
Juang Bhasha is an endangered Munda language spoken by the Juang indigenous community in eastern India, primarily in the state of Odisha.
-
D.
Kurukh
Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
-
E.
Arebhashe
Arebhashe is a Dravidian language variety spoken primarily by Gowda communities in parts of Karnataka and Kerala in southwestern India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afac95048190a5d1ef012899c62b |
completed | April 19, 2026, 10:34 a.m. |
Created at: April 10, 2026, 10:21 a.m.