Triple
T8294528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guntur district |
E194180
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Guntur |
E35413
|
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: Guntur | Statement: [Guntur district, hasCity, Guntur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Guntur Context triple: [Guntur district, hasCity, Guntur]
-
A.
Guntur
chosen
Guntur is a major city in the Indian state of Andhra Pradesh, known historically as an important administrative and commercial center in southeastern India.
-
B.
Kakinada
Kakinada is a coastal city in the Indian state of Andhra Pradesh, known for its port, seafood industry, and role as a regional commercial hub.
-
C.
Gudivada
Gudivada is a town in the Indian state of Andhra Pradesh known as a local commercial and educational center in the Krishna River delta region.
-
D.
Machilipatnam
Machilipatnam is a coastal city in the Indian state of Andhra Pradesh, historically known as a significant port and trading center on the Bay of Bengal.
-
E.
Khammam
Khammam is a city in the Indian state of Telangana known for its historical forts, temples, and proximity to the Munneru River.
- 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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7df5fff88190ac51a8d1c3eb2fe2 |
completed | March 31, 2026, 7:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf27abf324819098bd6ecfd5a4d8cc |
completed | April 3, 2026, 2:36 a.m. |
Created at: March 30, 2026, 5:52 p.m.