Triple
T8532300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nizhyn |
E201982
|
entity |
| Predicate | grantedMagdeburgRightsIn |
P19563
|
FINISHED |
| Object | 1625 |
—
|
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: 1625 | Statement: [Nizhyn, grantedMagdeburgRightsIn, 1625]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedMagdeburgRightsIn Context triple: [Nizhyn, grantedMagdeburgRightsIn, 1625]
-
A.
receivedMagdeburgRightsInYear
chosen
Indicates that an entity was granted Magdeburg rights in the specified year.
-
B.
wasFreeImperialCityOf
Indicates that an entity formerly held the status of a Free Imperial City within the Holy Roman Empire in relation to another specified entity (typically the empire or its imperial structure).
-
C.
dateOfPrussianHomage
Indicates the specific date on which the Prussian Homage event took place or was formally recorded.
-
D.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
E.
cityStatusGrantedIn
Indicates the event or point in time at which an entity was officially granted city status in a particular place or jurisdiction.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe676e2ac8190b65a3d2a935776fd |
completed | March 31, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:17 p.m.