Triple
T18477508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pururavas |
E451470
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Purūravas |
—
|
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: Purūravas | Statement: [Pururavas, alsoKnownAs, Purūravas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Purūravas Context triple: [Pururavas, alsoKnownAs, Purūravas]
-
A.
Pururavas
chosen
Pururavas is a legendary king in Hindu mythology, often regarded as an early lunar dynasty ruler and famed for his love story with the celestial nymph Urvashi.
-
B.
Bhurishravas
Bhurishravas is a warrior prince from the Mahabharata epic, known as a formidable Kaurava ally who meets his end on the battlefield of Kurukshetra.
-
C.
Vishrava
Vishrava is a revered sage in Hindu mythology, best known as the father of the demon king Ravana and his giant brother Kumbhakarna in the Ramayana.
-
D.
Shubrakhit
Shubrakhit is a town in Egypt’s Nile Delta region, located within the Beheira Governorate.
-
E.
Parshva
Parshva was a prominent Buddhist monk and scholar traditionally regarded as the presiding elder over the Fourth Buddhist Council convened under King Kanishka.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53064a7548190b712a14ad0c7a477 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 11:35 a.m.