Triple
T2749858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bihar |
E60958
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Chhapra |
E258584
|
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: Chhapra | Statement: [Bihar, containsCity, Chhapra]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chhapra Context triple: [Bihar, containsCity, Chhapra]
-
A.
Chhapra
chosen
Chhapra is a city in the Indian state of Bihar, known as the administrative headquarters of Saran district and a regional commercial and transportation hub along the Ganges River.
-
B.
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.
-
C.
Jamnagar
Jamnagar is a city in the Indian state of Gujarat, known for its oil refineries, brass industries, and proximity to the Gulf of Kutch.
-
D.
Shahjahanpur
Shahjahanpur is a prominent city in the Rohilkhand region of Uttar Pradesh, India, known for its historical significance and regional commercial importance.
-
E.
Harda
Harda is a town and administrative district headquarters in the central Indian state of Madhya Pradesh, known for its agricultural economy and railway connectivity.
- 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb52b1d48190b6ab511cc8834a14 |
completed | March 7, 2026, 8:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b055c4e58c8190809cc77161754246 |
completed | March 10, 2026, 5:32 p.m. |
Created at: March 6, 2026, 9:56 p.m.