Triple
T8654369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alwar State |
E205377
|
entity |
| Predicate | alternateName |
P39
|
FINISHED |
| Object | Ulwar State |
E749880
|
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: Ulwar State | Statement: [Alwar State, alternateName, Ulwar State]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulwar State Context triple: [Alwar State, alternateName, Ulwar State]
-
A.
Ulwar State
chosen
Ulwar State was a former princely state in British India, located in the region of present-day Rajasthan.
-
B.
Ngaraard State
Ngaraard State is one of the states of Palau, located on the island of Babeldaob and known for its traditional villages and coastal landscapes.
-
C.
Morvi State
Morvi State was a former princely state in western India, historically governed by the Jadeja Rajput dynasty.
-
D.
Balasinor State
Balasinor State was a former princely state in western India, located in present-day Gujarat and historically ruled by a Muslim dynasty under British suzerainty.
-
E.
Mewar State
Mewar State was a historic princely state in present-day Rajasthan, India, centered on the city of Udaipur and ruled for centuries by the Sisodia Rajput dynasty.
- 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_69cef373a22c8190931b4107c68e7017 |
completed | April 2, 2026, 10:53 p.m. |
Created at: March 30, 2026, 6:29 p.m.