Triple
T11422313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi NCR |
E270654
|
entity |
| Predicate | hasMajorCity |
P316
|
FINISHED |
| Object | Alwar |
E59873
|
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: Alwar | Statement: [Delhi NCR, hasMajorCity, Alwar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alwar Context triple: [Delhi NCR, hasMajorCity, Alwar]
-
A.
Alwar
chosen
Alwar is a historic city in northern India known for its forts, palaces, and proximity to the Sariska Tiger Reserve.
-
B.
Aalwar
Aalwar is a 2007 Tamil-language action drama film starring Ajith Kumar, known for its themes of revenge and vigilantism.
-
C.
Alwar State
Alwar State was a princely state in northern India, ruled by Rajput princes and later integrated into the modern state of Rajasthan after Indian independence.
-
D.
Kukanoor
Kukanoor is a historic village in Karnataka, India, known for its ancient temples and archaeological significance.
-
E.
Sholinghur
Sholinghur is a historic town in Tamil Nadu, India, known for its role in 18th-century Anglo-Mysore conflicts and its prominent hilltop temples.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801b357e88190ace56d36a945688f |
completed | April 9, 2026, 7:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5b8a1e88c8190994bea88a0490e60 |
completed | April 20, 2026, 5:24 a.m. |
Created at: April 8, 2026, 9:34 p.m.