Triple
T18562454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishakha |
E453678
|
entity |
| Predicate | associatedWithPlace |
P2830
|
FINISHED |
| Object | Vraja |
—
|
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: Vraja | Statement: [Vishakha, associatedWithPlace, Vraja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vraja Context triple: [Vishakha, associatedWithPlace, 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.
Dhara
Dhara was the historic capital city of the Paramara dynasty in central India, known as an important political and cultural center during the medieval period.
-
C.
Vani
Vani is a feminine given name commonly used in India, often associated with speech, eloquence, and the Hindu goddess Saraswati.
-
D.
Vani
Vani is a historic town in western Georgia’s Imereti region, known for its important archaeological sites from the ancient Colchian civilization.
-
E.
Brahvi
Brahvi is an alternative name for the Brahui language, a Dravidian language spoken primarily in Pakistan’s Balochistan region.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afb4f088190adf0b2b64057a210 |
completed | April 19, 2026, 8:28 p.m. |
Created at: April 10, 2026, 11:42 a.m.