Triple
T13053706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Uttar Pradesh |
E327511
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Raebareli |
E128995
|
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: Raebareli | Statement: [Central Uttar Pradesh, hasMajorCity, Raebareli]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raebareli Context triple: [Central Uttar Pradesh, hasMajorCity, Raebareli]
-
A.
Amroha
Amroha is a town and municipal board in Uttar Pradesh, India, known for its historical significance and cultural heritage.
-
B.
Rae Bareli
chosen
Rae Bareli is a city and prominent Lok Sabha constituency in the Indian state of Uttar Pradesh, long known as a stronghold of the Nehru–Gandhi political family.
-
C.
Azamgarh
Azamgarh is a city in the Purvanchal region of eastern Uttar Pradesh, India, known as an important cultural and educational center.
-
D.
Jaunpur
Jaunpur is a historic city in the Indian state of Uttar Pradesh, known for its medieval architecture and cultural heritage.
-
E.
Bulandshahr
Bulandshahr is a city in the Indian state of Uttar Pradesh known for its historical significance and proximity to Delhi within the broader metropolitan 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980bb52d88190b5be12000e27a2c9 |
completed | April 10, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d5ff8c308190a40274c68a1c5da3 |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 8:58 p.m.