Triple
T19789522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juhuri |
E475371
|
entity |
| Predicate | selfDesignation |
P974
|
FINISHED |
| Object | Juhuro |
—
|
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: Juhuro | Statement: [Juhuri, selfDesignation, Juhuro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Juhuro Context triple: [Juhuri, selfDesignation, Juhuro]
-
A.
Juhuri
Juhuri are a Jewish ethnic group from the Eastern Caucasus, traditionally speaking Judeo-Tat and maintaining distinct religious and cultural practices.
-
B.
Juho
Juho is a Finnish masculine given name historically borne by several notable figures, including statesmen and cultural personalities.
-
C.
Juha
Juha is a Finnish masculine given name commonly used in Finland and among Finnish speakers.
-
D.
Juh
Juh was a prominent Chiricahua Apache chief and war leader who played a key role in resisting U.S. and Mexican military forces during the Apache Wars.
-
E.
Juhurim
chosen
Juhurim are a Jewish ethnic group from the eastern and northern Caucasus, particularly Dagestan and Azerbaijan, with their own distinct language (Juhuri) and cultural traditions.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538ae5108190b80eb7de6f445f02 |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:49 p.m.