Triple
T9185370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundela dynasty |
E220442
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Datia |
E110279
|
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: Datia | Statement: [Bundela dynasty, capital, Datia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Datia Context triple: [Bundela dynasty, capital, Datia]
-
A.
Datia
chosen
Datia is a historic town and administrative center in central India, known for its palaces and temples, located in the state of Madhya Pradesh.
-
B.
Diass
Diass is a commune in western Senegal that hosts the country’s main international gateway, Blaise Diagne International Airport.
-
C.
Tarusa
Tarusa is a small historic town in western Russia known for its scenic location on the Oka River and its associations with Russian artists and writers.
-
D.
Dahegam
Dahegam is a town in the Indian state of Gujarat known for its local commerce and role as a regional hub within the Gandhinagar area.
-
E.
Dausa
Dausa is a town and district headquarters in the Indian state of Rajasthan, known for its historical forts, stepwells, and proximity to Jaipur.
- 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_69ca83e6d77c81909862b7afef56b1bf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc318d5c081908c50b56e5783ea38 |
completed | April 1, 2026, 7:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d05c19635c81908ad2cf07f5ad813c |
completed | April 4, 2026, 12:32 a.m. |
Created at: March 30, 2026, 7:24 p.m.