Triple
T2543421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peshwa |
E57839
|
entity |
| Predicate | basedIn |
P40
|
FINISHED |
| Object | Pune |
E14838
|
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: Pune | Statement: [Peshwa, basedIn, Pune]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pune Context triple: [Peshwa, basedIn, Pune]
-
A.
Pune
chosen
Pune is a major cultural, educational, and IT hub in the western Indian state of Maharashtra, known for its universities, historical significance, and rapidly growing urban economy.
-
B.
Nagpur
Nagpur is a major city in the Indian state of Maharashtra, known as a key political and commercial center and often referred to as the "Orange City" for its famous orange production.
-
C.
Nashik
Nashik is a historic city in the Indian state of Maharashtra, known for its religious significance in Hinduism and as a major center of wine production.
-
D.
Vadodara
Vadodara is a major city in western India known for its rich cultural heritage, educational institutions, and industrial development.
-
E.
Nanded
Nanded is a historic city in the Indian state of Maharashtra, known as an important Sikh pilgrimage center and a major urban hub in the Marathwada region.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2bf6cac819083a9ab9d041d8641 |
completed | March 7, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afaf3b61fc8190988484bedc5b57a0 |
completed | March 10, 2026, 5:42 a.m. |
Created at: March 6, 2026, 9:47 p.m.