Triple
T22652740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Марий Эл Республикасе |
E559135
|
entity |
| Predicate | ISO3166-2Code |
P208
|
FINISHED |
| Object | RU-ME |
—
|
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: RU-ME | Statement: [Марий Эл Республикасе, ISO3166-2Code, RU-ME]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RU-ME Context triple: [Марий Эл Республикасе, ISO3166-2Code, RU-ME]
-
A.
RU-ME
chosen
RU-ME is the ISO 3166-2 subdivision code assigned to the Republic of Mari El, a federal subject of Russia.
-
B.
RU-VOR
RU-VOR is the ISO 3166-2 regional code assigned to Voronezh Oblast, a federal subject in western Russia.
-
C.
RU-KOS
RU-KOS is the ISO 3166-2 subdivision code assigned to Kostroma Oblast, a federal subject in central Russia.
-
D.
RU-DA
RU-DA is the ISO 3166-2 regional code assigned to the Republic of Dagestan within the Russian Federation.
-
E.
RU-TY
RU-TY is the ISO 3166-2 subdivision code assigned to the Tuva Republic, a federal subject of Russia in southern Siberia.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703d7d648190aafe275cd04c47cf |
completed | April 29, 2026, 2:43 a.m. |
Created at: April 17, 2026, 3:06 p.m.