Triple
T8654342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alwar State |
E205377
|
entity |
| Predicate | capital |
P234
|
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: [Alwar State, capital, Alwar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alwar Context triple: [Alwar State, capital, 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.
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.
-
C.
Palamoor
Palamoor is the historical name of Mahbubnagar, a town and district headquarters in the Indian state of Telangana.
-
D.
Suratgarh
Suratgarh is a town in the northern Indian state of Rajasthan, known for its agricultural significance and military and air force establishments.
-
E.
Goverdhan
Goverdhan is a legislative assembly constituency in Uttar Pradesh, India, known for encompassing the pilgrimage town of Govardhan near Mathura.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48432568819093b9a867b4f62b78 |
completed | March 31, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ceccdaad2881908f131ee9da2841d1 |
completed | April 2, 2026, 8:08 p.m. |
Created at: March 30, 2026, 6:29 p.m.