Triple
T13356672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kumaoni people |
E318710
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Kausani |
E316743
|
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: Kausani | Statement: [Kumaoni people, region, Kausani]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kausani Context triple: [Kumaoni people, region, Kausani]
-
A.
Kausani
chosen
Kausani is a scenic hill town in Uttarakhand, India, renowned for its panoramic Himalayan views and tranquil natural surroundings.
-
B.
Kadamtala
Kadamtala is a small settlement located on Middle Andaman Island in the Andaman and Nicobar Islands of India.
-
C.
Kasarani
Kasarani is a residential and commercial suburb in northeastern Nairobi, Kenya, known for hosting major sports and educational facilities.
-
D.
Kanyākubja
Kanyākubja is an ancient North Indian city of great historical and cultural significance, known today as Kannauj.
-
E.
Kausani region
Kausani region is a scenic hill area in Uttarakhand, India, renowned for its panoramic Himalayan views and tranquil natural surroundings.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd4cb008190af99c4856e76ac08 |
completed | April 11, 2026, 11:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f72677b2a48190aad30f3ee6cacefb |
completed | May 3, 2026, 10:41 a.m. |
Created at: April 9, 2026, 9:32 p.m.