Triple
T24792321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Миџор |
E620282
|
entity |
| Predicate | имеНаЋирилици |
P157137
|
FINISHED |
| Object | Миџор |
—
|
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: Миџор | Statement: [Миџор, имеНаЋирилици, Миџор]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеНаЋирилици Context triple: [Миџор, имеНаЋирилици, Миџор]
-
A.
usesKatakanaFor
Indicates that one entity is written or represented using katakana script in relation to another entity.
-
B.
romanizedUnder
Indicates that one written form is a romanized representation (using the Latin alphabet) of another form written in a different script.
-
C.
nameInJapaneseKana
Indicates that an entity’s name is written or represented using Japanese kana characters.
-
D.
onYomiJapanese
Indicates that the specified reading is the on’yomi (Sino-Japanese) pronunciation associated with a given kanji or term.
-
E.
nameInMcCuneReischauer
Indicates that an entity’s name is represented using the McCune–Reischauer romanization system.
- F. None of above. chosen
Provenance (4 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4110424188190889a13976b16b18a |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f410a001788190a457e41f53aaf90c |
completed | May 1, 2026, 2:32 a.m. |
Created at: April 18, 2026, 4:47 a.m.