Triple
T21245856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Александр Миротворец |
E523605
|
entity |
| Predicate | используетсяДляОбозначения |
P6238
|
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 something is used together with or by means of another entity.
-
B.
designationUsedFor
chosen
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
C.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another entity.
-
D.
designationUse
Indicates how a particular designation or title is intended to be used or applied in relation to an entity.
-
E.
usedToMark
Indicates that one entity serves as a marker, label, or indicator for another entity.
- 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.