Triple
T13610952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coorg |
E325184
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Kushalnagar |
E344783
|
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: Kushalnagar | Statement: [Coorg, contains, Kushalnagar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kushalnagar Context triple: [Coorg, contains, Kushalnagar]
-
A.
Kushalnagar
chosen
Kushalnagar is a town in Karnataka’s Kodagu district, known as a gateway to the Coorg region and nearby river, dam, and nature attractions.
-
B.
Hoshangabad
Hoshangabad is a city in the Indian state of Madhya Pradesh, known for its location on the banks of the Narmada River and its agricultural and industrial activities.
-
C.
Jagdishpur
Jagdishpur is a town in the Bhojpur district of Bihar, India, historically known as the ancestral estate of the 19th-century freedom fighter Kunwar Singh.
-
D.
Himmatnagar
Himmatnagar is a town in the Sabarkantha district of Gujarat, India, known as a regional commercial and administrative center.
-
E.
Nagole
Nagole is a residential and commercial neighborhood in Hyderabad, India, served as a key terminus and transit hub on the Hyderabad Metro network.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0aa9a1481908c6f92495aff86c6 |
completed | April 12, 2026, 2:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b05f0e948190b7f22d071ad54283 |
completed | May 3, 2026, 8:30 p.m. |
Created at: April 9, 2026, 9:50 p.m.