Triple
T19422217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaunsar-Bawar region |
E485883
|
entity |
| Predicate | hasSubregion |
P285
|
FINISHED |
| Object | Jaunsar |
—
|
NE NERFINISHED |
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: Jaunsar | Statement: [Jaunsar-Bawar region, hasSubregion, Jaunsar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jaunsar Context triple: [Jaunsar-Bawar region, hasSubregion, Jaunsar]
-
A.
Jaunsari
chosen
Jaunsari is an Indo-Aryan language spoken by the Jaunsari people in the Jaunsar-Bawar region of northern India.
-
B.
Jekabpils
Jekabpils is a town in southeastern Latvia known for its historic architecture and scenic location along the Daugava River.
-
C.
Jaunliepāja
Jaunliepāja is a district of the Latvian port city of Liepāja, known for its mix of residential areas and industrial heritage near the Baltic Sea coast.
-
D.
Rietavas
Rietavas is a historic town in western Lithuania, known as one of the main centers of the Samogitian region.
-
E.
Jaunpils
Jaunpils is a small historic town in western Latvia known for its medieval castle and rural surroundings.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e632159d7081909d004544ec5992c0 |
completed | April 20, 2026, 2:03 p.m. |
Created at: April 10, 2026, 1:37 p.m.