Triple
T16062395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hisar Lok Sabha constituency |
E389642
|
entity |
| Predicate | hasMajorTown |
P316
|
FINISHED |
| Object | Adampur |
E1192081
|
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: Adampur | Statement: [Hisar Lok Sabha constituency, hasMajorTown, Adampur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adampur Context triple: [Hisar Lok Sabha constituency, hasMajorTown, Adampur]
-
A.
Adampur
chosen
Adampur is a town and legislative assembly constituency in the Hisar district of Haryana, India, known for its political significance in the region.
-
B.
Vikrampur
Vikrampur was a historic urban and political center in the Bengal region, renowned as an important seat of power and culture in medieval South Asia.
-
C.
Daryapur
Daryapur is a town in the Amravati district of Maharashtra, India, known for its agricultural economy and regional market activities.
-
D.
Ramdaspur
Ramdaspur is the historical name for the city of Amritsar in Punjab, India, a major spiritual and cultural center of Sikhism.
-
E.
Sikandarpur
Sikandarpur is a metro station in the Delhi Metro network that serves the Gurugram area and provides an interchange with the Rapid Metro system.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1837a04108190b5a1dbbe2063039e |
completed | April 17, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb8cca308190875432a5cf5f8616 |
completed | May 10, 2026, 2:21 a.m. |
Created at: April 10, 2026, 4:57 a.m.