Triple
T11444639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alwar district |
E271231
|
entity |
| Predicate | hasMajorTown |
P316
|
FINISHED |
| Object | Neemrana |
E928309
|
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: Neemrana | Statement: [Alwar district, hasMajorTown, Neemrana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neemrana Context triple: [Alwar district, hasMajorTown, Neemrana]
-
A.
Neemrana
chosen
Neemrana is a historic town in Rajasthan, India, best known for its restored 15th-century hilltop fort palace that now operates as a heritage hotel and popular tourist destination.
-
B.
Neemuch
Neemuch is a town in northwestern Madhya Pradesh, India, known as an important agricultural and trading center and for hosting a significant military cantonment.
-
C.
Jwalapur
Jwalapur is a prominent suburban town and commercial hub near Haridwar in the Indian state of Uttarakhand.
-
D.
Khandala
Khandala is a popular hill station in Maharashtra, India, known for its scenic valleys, waterfalls, and trekking spots in the Western Ghats.
-
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_69d6aadff8888190a13f253f0d460874 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8088a66f48190b2b4a56cd62097cf |
completed | April 9, 2026, 8:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e624782cf88190b696a1c7c9a56395 |
completed | April 20, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:35 p.m.