Triple
T17391187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenegrin Latin alphabet |
E422825
|
entity |
| Predicate | ISO15924Code |
P208
|
FINISHED |
| Object | Latn |
—
|
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: Latn | Statement: [Montenegrin Latin alphabet, ISO15924Code, Latn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Latn Context triple: [Montenegrin Latin alphabet, ISO15924Code, Latn]
-
A.
Latn
chosen
Latn is the ISO 15924 script code representing the Latin alphabet used for writing numerous modern languages worldwide.
-
B.
Latuvi
Latuvi is a small rural village in the Sierra Norte region of Oaxaca, Mexico, known for its mountainous landscapes and traditional indigenous culture.
-
C.
Latynina
Latynina is a Russian surname most famously associated with Larisa Latynina, one of the most decorated gymnasts in Olympic history.
-
D.
Latgalian
Latgalian is an Eastern Baltic language variety closely related to Latvian, traditionally spoken by the Latgalian ethnic group in the Latgale region of eastern Latvia.
-
E.
Latvian
Latvian is a Baltic language spoken primarily in Latvia and one of the official languages of the European Union.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43aba5398819096846bdeefde0788 |
completed | April 19, 2026, 2:15 a.m. |
Created at: April 10, 2026, 5:45 a.m.