Triple
T21718043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaunsari language |
E536082
|
entity |
| Predicate | ethnicity |
P194
|
FINISHED |
| Object | Jaunsari |
—
|
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: Jaunsari | Statement: [Jaunsari language, ethnicity, Jaunsari]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jaunsari Context triple: [Jaunsari language, ethnicity, Jaunsari]
-
A.
Jaunsari
chosen
Jaunsari is an Indo-Aryan language spoken by the Jaunsari people in the Jaunsar-Bawar region of northern India.
-
B.
Sakiai
Sakiai is a small town in southwestern Lithuania known for its proximity to the Russian and Polish borders and its role as a local administrative and cultural center.
-
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.
Vaiņode
Vaiņode is a small town in western Latvia, situated in the historical region of Kurzeme.
-
E.
Kalsnava
Kalsnava is a settlement in eastern Latvia known for its surrounding forests and inclusion within Madona Municipality.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96babdc81908226ec043dbe7431 |
completed | April 27, 2026, 9:47 p.m. |
Created at: April 16, 2026, 6:47 p.m.