Triple
T10406447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pusa, Bihar |
E245274
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Samastipur |
E311154
|
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: Samastipur | Statement: [Pusa, Bihar, locatedNear, Samastipur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Samastipur Context triple: [Pusa, Bihar, locatedNear, Samastipur]
-
A.
Samastipur
chosen
Samastipur is a city in the Indian state of Bihar known as an important railway junction and agricultural trade center in the region.
-
B.
Saharsa
Saharsa is a city in the northeastern Indian state of Bihar, known as a major agricultural and commercial center in the Kosi river region.
-
C.
Neemuch
Neemuch is a town in northwestern Madhya Pradesh, India, known as an important agricultural and trading center and for hosting a significant military cantonment.
-
D.
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.
-
E.
Bhagalpur
Bhagalpur is a historic city in the eastern Indian state of Bihar, known for its silk industry and location along the Ganges River.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9f834288190a0df246974ffaea8 |
completed | April 7, 2026, 11:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d94af4ee6881909a36ee1a06a9d3e2 |
completed | April 10, 2026, 7:09 p.m. |
Created at: April 6, 2026, 12:08 p.m.