Triple
T14249501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ameerpet |
E353219
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Begumpet |
E1082308
|
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: Begumpet | Statement: [Ameerpet, adjacentTo, Begumpet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Begumpet Context triple: [Ameerpet, adjacentTo, Begumpet]
-
A.
Begumpet
chosen
Begumpet is a prominent neighborhood in Hyderabad, India, known for its commercial centers, residential areas, and historical significance as the site of the former Begumpet Airport.
-
B.
Bakumpai
The Bakumpai are an indigenous Dayak ethnic group of central Kalimantan, Indonesia, traditionally living along the Barito River and known for their distinct language and river-based culture.
-
C.
Bengan
Bengan is a Swedish diminutive or nickname commonly used for the male given name Bengt.
-
D.
Bompoka
Bompoka is a small, remote island that forms part of India’s Nicobar Islands archipelago in the eastern Indian Ocean.
-
E.
Ngaluma
Ngaluma is an Aboriginal Australian people traditionally associated with the coastal and inland regions of the Pilbara in Western Australia.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6295ef9081909cfb0c1283bca21a |
completed | April 14, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd325815d48190b070866f41986847 |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:08 a.m.