Triple
T34962678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Могилёв-Подольский |
E1008301
|
entity |
| Predicate | получилМагдебургскоеПраво |
P19563
|
FINISHED |
| Object | XVII век |
—
|
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: XVII век | Statement: [Могилёв-Подольский, получилМагдебургскоеПраво, XVII век]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: получилМагдебургскоеПраво Context triple: [Могилёв-Подольский, получилМагдебургскоеПраво, XVII век]
-
A.
receivedMagdeburgRightsInYear
chosen
Indicates that an entity was granted Magdeburg rights in the specified year.
-
B.
hasVoivodeshipRights
Indicates that an entity possesses the legal status, privileges, or jurisdictional authority associated with a voivodeship (a regional administrative unit).
-
C.
intendedStatusOfGrandDuchyOfRuthenia
Indicates the planned or desired political or legal status assigned to the Grand Duchy of Ruthenia.
-
D.
papalBull
Indicates that a formal decree, charter, or proclamation has been issued by the Pope regarding the related entity or matter.
-
E.
acquiredPrincipality
Indicates that one entity obtained control or ownership of a principality from another or through some specified means.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.