Triple
T653395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wieliczka |
E11392
|
entity |
| Predicate | receivedTownRights |
P3431
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Wieliczka, receivedTownRights, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedTownRights Context triple: [Wieliczka, receivedTownRights, 13th century]
-
A.
grantedTownRights
chosen
Indicates that an authority formally conferred municipal or town privileges and legal status upon a settlement.
-
B.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
-
C.
typicalRegionRights
Indicates that certain rights or permissions are characteristic or standard for a given region.
-
D.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
E.
historicalRightGranted
Indicates that a right or privilege was formally granted to an entity at some point in the past.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4a660c8190b887cb4da01ef7ae |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d1001088190aa7ca3c8f2ad0e32 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.