Triple
T22292844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bal Gandharva |
E551040
|
entity |
| Predicate | honorific |
P301
|
FINISHED |
| Object | Gandharva |
—
|
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: Gandharva | Statement: [Bal Gandharva, honorific, Gandharva]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gandharva Context triple: [Bal Gandharva, honorific, Gandharva]
-
A.
Gandharvas
chosen
Gandharvas are celestial musicians and singers in Hindu and Buddhist mythology, renowned for their beauty, artistry, and role in entertaining the gods.
-
B.
Trilokasara
Trilokasara is a significant Jain philosophical text that systematically describes the structure and nature of the three worlds (loka) in Jain cosmology.
-
C.
Vaishvanara
Vaishvanara is a Vedic epithet of the fire god Agni, emphasizing his universal, all-pervading aspect as the cosmic fire present in all beings.
-
D.
Yagnik
Yagnik is an Indian surname commonly associated with Gujarati families and notable figures in politics, arts, and public life.
-
E.
Вахандарья
Вахандарья — горная река в Таджикистане, один из истоков реки Пяндж, протекающая по высокогорным районам Памира.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1560de3508190951ad0806ae3cc0d |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 16, 2026, 8:41 p.m.