Triple
T21245870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Александр Миротворец |
E523605
|
entity |
| Predicate | семантическаяКатегория |
P7975
|
FINISHED |
| Object | личное прозвище |
—
|
LITERAL FINISHED |
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.
семантическоеПоле
Indicates that entities are related by belonging to the same semantic field, i.e., they share a common area of meaning or conceptual domain.
-
B.
semanticType
chosen
Indicates that something belongs to or is categorized under a particular semantic class or type based on its meaning.
-
C.
hasMeaningCategory
Indicates that something is associated with a particular category of meaning or semantic type.
-
D.
semanticsDetail
Indicates a more specific or fine-grained semantic characterization or nuance of a broader meaning or interpretation.
-
E.
semanticRootMeaning
Indicates the fundamental or core meaning that underlies a word, phrase, or expression in a semantic structure.
- F. None of above.
Provenance (3 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_69e0b513b89c81908b27147e91368db2 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73599e5548190ad70d2c2bfa9e919 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:49 p.m.