Triple
T18781934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulshanabad (Medak) administrative division |
E459277
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Gulshanabad |
—
|
NE NERFINISHED |
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: Gulshanabad | Statement: [Gulshanabad (Medak) administrative division, namedAfter, Gulshanabad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gulshanabad Context triple: [Gulshanabad (Medak) administrative division, namedAfter, Gulshanabad]
-
A.
Gulshanabad
chosen
Gulshanabad is a locality in the Medak region of Telangana, India, known primarily as the namesake of the Gulshanabad (Medak) administrative division.
-
B.
Gulshanabad
Gulshanabad is the former historical name of the Indian city now known as Nashik in Maharashtra.
-
C.
Shahabad
Shahabad is a town in the Kurukshetra district of Haryana, India, known historically by its former name Shahbad Markanda.
-
D.
Shahabad
Shahabad is a town in Uttar Pradesh, India, situated within the administrative boundaries of Rampur district.
-
E.
Shamshabad
Shamshabad is a suburban area near Hyderabad in the Indian state of Telangana, known primarily for hosting the Rajiv Gandhi International Airport.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5977d7c5c8190ab2aadb47283965d |
completed | April 20, 2026, 3:03 a.m. |
Created at: April 10, 2026, 11:52 a.m.