Triple
T5300375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Awadhi |
E119962
|
entity |
| Predicate | spokenIn |
P2266
|
FINISHED |
| Object | Lucknow region |
E133975
|
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: Lucknow region | Statement: [Awadhi, spokenIn, Lucknow region]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lucknow region Context triple: [Awadhi, spokenIn, Lucknow region]
-
A.
Lucknow district
chosen
Lucknow district is an administrative region in the Indian state of Uttar Pradesh that encompasses the city of Lucknow and its surrounding areas.
-
B.
southeastern Uttar Pradesh
Southeastern Uttar Pradesh is a region in northern India known for its Hindi–Bagheli speaking population and its location along the middle Ganges basin.
-
C.
Rohilkhand
Rohilkhand is a historical region in northern India, located in present-day Uttar Pradesh, known for its Rohilla Afghan heritage and fertile Gangetic plains.
-
D.
Agra division
Agra division is an administrative division in the Indian state of Uttar Pradesh that includes the city of Agra and surrounding districts.
-
E.
Delhi region
The Delhi region is a historic cultural and political heartland of northern India centered on the city of Delhi and its surrounding areas.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd850877688190a611d6293ca58d94 |
completed | March 20, 2026, 5:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf21b22be08190ad5d3d6b12b80bcb |
completed | March 21, 2026, 10:54 p.m. |
Created at: March 20, 2026, 1:53 p.m.