Triple
T17958197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haryana Urban Development Authority |
E449006
|
entity |
| Predicate | regionServed |
P82
|
FINISHED |
| Object | Palwal |
E404401
|
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: Palwal | Statement: [Haryana Urban Development Authority, regionServed, Palwal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Palwal Context triple: [Haryana Urban Development Authority, regionServed, Palwal]
-
A.
Palwal
chosen
Palwal is a city in the Indian state of Haryana that forms part of the extended urban area surrounding Delhi.
-
B.
Rampur
Rampur is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
-
C.
Rampur
Rampur is a prominent city in the Rohilkhand region of Uttar Pradesh, India, known historically for its princely state heritage and distinctive Rampuri culture.
-
D.
Rampur
Rampur is a town located in Nepal's Palpa District, known as one of the local settlements in the hilly western region of the country.
-
E.
Ishwarpur
Ishwarpur is a municipality-level city located in Nepal’s Madhesh Province.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afb16bfc8190b3eb433a90f0630d |
completed | April 19, 2026, 10:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0397ebabcc81908e6cfe983afcb943 |
completed | May 12, 2026, 9:13 p.m. |
Created at: April 10, 2026, 10:21 a.m.