Triple
T11562582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohilla |
E274179
|
entity |
| Predicate | historicalCapital |
P2536
|
FINISHED |
| Object | Rampur |
E231615
|
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: Rampur | Statement: [Rohilla, historicalCapital, Rampur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rampur Context triple: [Rohilla, historicalCapital, Rampur]
-
A.
Rampur
Rampur is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
-
B.
Rampur
chosen
Rampur is a prominent city in the Rohilkhand region of Uttar Pradesh, India, known historically for its princely state heritage and distinctive Rampuri culture.
-
C.
Saharanpur
Saharanpur is a city in the Indian state of Uttar Pradesh known as a commercial and transportation hub, particularly for its wood carving industry and agricultural trade.
-
D.
Hamirpur
Hamirpur is a town and district headquarters in the Bundelkhand region of Uttar Pradesh, India, known for its location near the confluence of the Yamuna and Betwa rivers.
-
E.
Hajipur
Hajipur is a prominent city in the Indian state of Bihar, known as an important railway and commercial hub located near the state capital, Patna.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd2016481909b33848af3d1d6c1 |
completed | April 10, 2026, 5:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e713bcc0048190bec14ac4ab84d51d |
completed | April 21, 2026, 6:05 a.m. |
Created at: April 8, 2026, 9:37 p.m.