Triple
T4872037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NH 44 |
E109106
|
entity |
| Predicate | connectsCity |
P4245
|
FINISHED |
| Object | Kurnool |
E201854
|
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: Kurnool | Statement: [NH 44, connectsCity, Kurnool]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kurnool Context triple: [NH 44, connectsCity, Kurnool]
-
A.
Kurnool
chosen
Kurnool is a prominent city in the Indian state of Andhra Pradesh, known historically as a former capital and a key commercial and educational center in the region.
-
B.
Nellore
Nellore is a prominent coastal city in southeastern India known for its agriculture, aquaculture, and role as an administrative and commercial center in Andhra Pradesh.
-
C.
Rajahmundry
Rajahmundry is a historic city in the Indian state of Andhra Pradesh, known as a major cultural and commercial center in the Godavari region.
-
D.
Guntur
Guntur is a major city in the Indian state of Andhra Pradesh, known historically as an important administrative and commercial center in southeastern India.
-
E.
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.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d9e27908190a0c4540ee2559c4b |
completed | March 20, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69becfa0b4fc8190bf9ee8abf1684503 |
completed | March 21, 2026, 5:04 p.m. |
Created at: March 20, 2026, 1:27 p.m.