Triple
T19625365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rewari district |
E471119
|
entity |
| Predicate | hasMajorTown |
P316
|
FINISHED |
| Object | Rewari |
—
|
NE NERFINISHED |
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: Rewari | Statement: [Rewari district, hasMajorTown, Rewari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rewari Context triple: [Rewari district, hasMajorTown, Rewari]
-
A.
Rewari
chosen
Rewari is a historic city in the Indian state of Haryana, located near Delhi and known for its brass industry and strategic position in northern India.
-
B.
Bhiwani
Bhiwani is a city in the Indian state of Haryana known as a regional educational and political hub.
-
C.
Rohtak
Rohtak is a major city in the Indian state of Haryana, known as an educational and administrative center within the National Capital Region.
-
D.
Saharanpur
Saharanpur is a city in the Indian state of Uttar Pradesh known as a commercial and transportation hub, particularly for its wood carving industry and agricultural trade.
-
E.
Ambala
Ambala is a historic city and important military and transportation hub in the northern Indian state of Haryana.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e92ff48190ae6e6ba2c603d5e7 |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:44 p.m.