Triple
T21245858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Александр Миротворец |
E523605
|
entity |
| Predicate | ассоциируетсяСРолью |
P2830
|
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.
associatedWithUnitRole
Indicates that an entity has a connection or linkage to a specific role within a particular unit or organizational subdivision.
-
B.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
-
C.
associatedCollectiveRole
Indicates that an entity is linked to a role or function held within a collective, group, or organization.
-
D.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
associatedWithTitleHolderRole
Indicates a relationship where an entity is connected to, or linked with, a role held by a title holder.
- 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.