Triple
T19731161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Virata |
E473855
|
entity |
| Predicate | fatherOf |
P120
|
FINISHED |
| Object | Shveta |
—
|
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: Shveta | Statement: [King Virata, fatherOf, Shveta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shveta Context triple: [King Virata, fatherOf, Shveta]
-
A.
Shveta
chosen
Shveta is a character in the Indian epic Mahabharata, known as a prince of the Matsya kingdom and son of King Virata.
-
B.
Sveta
Sveta is a common Russian diminutive form of the female given name Svetlana, often used as an affectionate or informal nickname.
-
C.
Malisheva
Malisheva is a town and municipality in central Kosovo known for its location in the historical Dukagjin region and its role as a local administrative and economic center.
-
D.
Vika
Vika is a central neighborhood in Oslo, Norway, known for its waterfront location, cultural institutions, and proximity to the city’s business district.
-
E.
Yakushova
Yakushova is a Russian surname, notably borne by Nina Ivanovna Yakushova.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e649fd18148190a6e85b2be0069dde |
completed | April 20, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:47 p.m.