Triple
T4986869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Braj region |
E112023
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Vraja |
E484343
|
NE FINISHED |
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: Vraja | Statement: [Braj region, alsoKnownAs, Vraja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vraja Context triple: [Braj region, alsoKnownAs, Vraja]
-
A.
Vraj
chosen
Vraj is a culturally and religiously significant region in northern India associated with the life and legends of the Hindu deity Krishna.
-
B.
Vani
Vani is a historic town in western Georgia’s Imereti region, known for its important archaeological sites from the ancient Colchian civilization.
-
C.
Vrishni
Vrishni was a prominent clan within the ancient Yadava lineage of India, traditionally associated with Lord Krishna and centered around the region of Mathura and Dvaraka.
-
D.
Veeragase
Veeragase is a vigorous and ritualistic folk dance-drama of Karnataka, India, traditionally performed during festivals to depict stories of valor from Hindu mythology.
-
E.
Braj
Braj is a culturally significant region in northern India traditionally associated with the life and legends of the Hindu deity Krishna.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd727c25bc8190b72f6ddd3772c80a |
completed | March 20, 2026, 4:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be924f11c88190abe6263bf11b848c |
completed | March 21, 2026, 12:42 p.m. |
Created at: March 20, 2026, 1:34 p.m.