Triple
T11860457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SITE Town |
E282143
|
entity |
| Predicate | hasNeighbourhood |
P4813
|
FINISHED |
| Object | Mominabad |
E282144
|
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: Mominabad | Statement: [SITE Town, hasNeighbourhood, Mominabad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mominabad Context triple: [SITE Town, hasNeighbourhood, Mominabad]
-
A.
Mominabad
chosen
Mominabad is a residential neighborhood located within the Karachi West District of Karachi, Pakistan.
-
B.
Murtazabad
Murtazabad is a village in the Lower Hunza region of northern Pakistan, known for its mountainous landscape and proximity to the Hunza River.
-
C.
Nasirabad
Nasirabad is a town and administrative area located in the Balochistan region of present-day Pakistan.
-
D.
Nasirabad
Nasirabad is a village in the Lower Hunza region of northern Pakistan, known for its mountainous terrain and proximity to the Karakoram Range.
-
E.
Mehmedabad
Mehmedabad is a town in the Kheda district of Gujarat, India, known for its historical significance and location along key regional transport routes.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69a099c8190a674db64c50eca5a |
completed | April 10, 2026, 7:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f281745ca88190968e1f674d0e483c |
completed | April 29, 2026, 10:08 p.m. |
Created at: April 8, 2026, 9:43 p.m.