Triple
T19810705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhishma |
E475935
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Ganga-putra |
—
|
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: Ganga-putra | Statement: [Bhishma, alsoKnownAs, Ganga-putra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ganga-putra Context triple: [Bhishma, alsoKnownAs, Ganga-putra]
-
A.
Gangaputra
chosen
Gangaputra is an epithet of Bhishma, the revered warrior and elder statesman of the Indian epic Mahabharata, highlighting his divine lineage as the son of the river goddess Ganga.
-
B.
Suryaputra
Suryaputra is an epithet of the legendary warrior Karna from the Indian epic Mahabharata, highlighting his divine parentage as the son of the sun god Surya.
-
C.
Dasaratha
Dasaratha is the legendary king of Ayodhya in the Hindu epic Ramayana and the father of Lord Rama.
-
D.
Pavanputra
Pavanputra is a revered epithet of the Hindu deity Hanuman, highlighting his divine parentage as the son of the wind god.
-
E.
Gunabhadra
Gunabhadra was a prominent Jain poet and scholar associated with the Rashtrakuta dynasty, known for his significant contributions to medieval Indian religious and literary traditions.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6542bd7a48190acf67db41f1131c9 |
completed | April 20, 2026, 4:28 p.m. |
Created at: April 10, 2026, 1:50 p.m.