Triple
T4962872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satna |
E111450
|
entity |
| Predicate | nearbyCity |
P350
|
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: [Satna, nearbyCity, Rewa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rewa Context triple: [Satna, nearbyCity, 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.
Rewa
Rewa is a coastal village in northern Poland situated along the Baltic Sea, known for its sandy beaches and popular windsurfing and kitesurfing conditions.
-
D.
Kareli
Kareli is a town in central Georgia that serves as an important local center within the Shida Kartli region.
-
E.
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.
- 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_69bd4419393c819086319a6fe4bf8542 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71f3e6148190b99f35734220ffc3 |
completed | March 20, 2026, 4:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be81ea8cc08190af40098ca99364f1 |
completed | March 21, 2026, 11:32 a.m. |
Created at: March 20, 2026, 1:32 p.m.