Triple
T2829061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reva |
E62191
|
entity |
| Predicate | isKnownAs |
P39
|
FINISHED |
| Object | Rewa |
E110278
|
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: Rewa | Statement: [Reva, isKnownAs, Rewa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rewa Context triple: [Reva, isKnownAs, Rewa]
-
A.
Rewa
Rewa is an alternative name for the Narmada River, one of central India's major and holiest rivers.
-
B.
Rewa
chosen
Rewa is a prominent city in northeastern Madhya Pradesh, India, known historically as the seat of the former Rewa princely state and for its cultural and administrative significance in the region.
-
C.
Kareli
Kareli is a town in central Georgia that serves as an important local center within the Shida Kartli region.
-
D.
Umaria
Umaria is a town and district headquarters in the central Indian state of Madhya Pradesh, known as a gateway to the nearby Bandhavgarh National Park.
-
E.
Shivpuri
Shivpuri is a historic town and former princely state in central India, known for its forests, wildlife sanctuaries, and royal palaces.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abde97168c8190b31122b2ad9fdebf |
completed | March 7, 2026, 8:15 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afceb4f3ec8190987afb7a2ac302e2 |
completed | March 10, 2026, 7:56 a.m. |
Created at: March 6, 2026, 10:01 p.m.