Triple
T5182024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daugavpils |
E116942
|
entity |
| Predicate | receivedTownRightsInCentury |
P3431
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Daugavpils, receivedTownRightsInCentury, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedTownRightsInCentury Context triple: [Daugavpils, receivedTownRightsInCentury, 16th century]
-
A.
receivedMagdeburgRightsInYear
Indicates that an entity was granted Magdeburg rights in the specified year.
-
B.
grantedTownRights
chosen
Indicates that an authority formally conferred municipal or town privileges and legal status upon a settlement.
-
C.
affirmedInCentury
Indicates that a statement, belief, or status was formally confirmed or upheld during a specified century.
-
D.
ruledUntilCentury
Indicates that a ruling relationship held by an entity continued in effect up to (but not necessarily including) a specified century.
-
E.
ruledFromCentury
Indicates that a ruling or governance relationship is associated with a specific century during which it took place.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd799bc58c819098a8e91e21baaef4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b7e8b4819092ec3965e11f2dea |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.