Triple
T16928715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Łowicz |
E410645
|
entity |
| Predicate | receivedMagdeburgRights |
P19563
|
FINISHED |
| Object | 1298 |
—
|
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: 1298 | Statement: [Łowicz, receivedMagdeburgRights, 1298]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedMagdeburgRights Context triple: [Łowicz, receivedMagdeburgRights, 1298]
-
A.
receivedMagdeburgRightsInYear
chosen
Indicates that an entity was granted Magdeburg rights in the specified year.
-
B.
reservedRightsToCrown
Indicates that certain legal powers, privileges, or interests are retained by the Crown rather than being transferred or granted away.
-
C.
grantedImperialImmediacyBy
Indicates that an entity received the special legal-political status of imperial immediacy directly from a specified imperial authority.
-
D.
feudalRights
Indicates that one party holds traditional feudal privileges, claims, or entitlements over another party or resource within a hierarchical lord–vassal structure.
-
E.
yearOfEdictOfRestitution
Indicates the specific calendar year in which the Edict of Restitution was issued.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf23873c8190bdc9121d6c3850e2 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.