Triple
T22824071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tukoji Rao Holkar II |
E565302
|
entity |
| Predicate | house |
P1505
|
FINISHED |
| Object | Holkar |
—
|
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: Holkar | Statement: [Tukoji Rao Holkar II, house, Holkar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holkar Context triple: [Tukoji Rao Holkar II, house, Holkar]
-
A.
Holkar
chosen
Holkar refers to a prominent Maratha dynasty that ruled the Indore State in central India and played a significant role in 18th- and 19th-century Indian politics.
-
B.
Talwandi Bhai
Talwandi Bhai is a small town in Punjab, India, known primarily as an agricultural and grain market hub.
-
C.
Balharshah
Balharshah is a key railway junction town in Maharashtra, India, serving as an important transit point on major north–south and east–west rail routes.
-
D.
Behari
Behari is a fictional character, likely from South Asian literature or drama, connected to the character Ashalata in a significant narrative relationship.
-
E.
Sarwan
Sarwan is a small town located in the Dumka district of Jharkhand, India.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dd34a248190881f2bccdd9aedce |
completed | April 29, 2026, 3:41 a.m. |
Created at: April 17, 2026, 3:34 p.m.