Triple
T11820718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salbai |
E281118
|
entity |
| Predicate | hasNameInEnglish |
P3437
|
FINISHED |
| Object | Salbai |
E281118
|
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: Salbai | Statement: [Salbai, hasNameInEnglish, Salbai]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Salbai Context triple: [Salbai, hasNameInEnglish, Salbai]
-
A.
Salbai
chosen
Salbai is a historical location in India known primarily as the site where the 1782 Treaty of Salbai was concluded between the British East India Company and the Maratha Empire.
-
B.
Bhabra
Bhabra is a town in the Alirajpur district of Madhya Pradesh, India, known as the birthplace of Indian revolutionary Chandra Shekhar Azad.
-
C.
Sohrai
Sohrai is a traditional harvest and cattle-worship festival celebrated by the Santal people, marked by ritual observances, feasting, and distinctive wall paintings.
-
D.
Yaganti
Yaganti is a historic temple town in Andhra Pradesh, India, renowned for its ancient Sri Yagantiswamy (Shiva) temple and distinctive rock formations.
-
E.
Sankhali
Sankhali is a village located in the North Goa district of the Indian state of Goa.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e87e488190905bc3bb6d721e56 |
completed | April 10, 2026, 7:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f28110623481908354bdd4e437f99e |
completed | April 29, 2026, 10:07 p.m. |
Created at: April 8, 2026, 9:42 p.m.