Triple
T1121306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrzanów |
E24617
|
entity |
| Predicate | townRightsGranted |
P3431
|
FINISHED |
| Object | before 1350 |
—
|
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: before 1350 | Statement: [Chrzanów, townRightsGranted, before 1350]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: townRightsGranted Context triple: [Chrzanów, townRightsGranted, before 1350]
-
A.
grantedTownRights
chosen
Indicates that an authority formally conferred municipal or town privileges and legal status upon a settlement.
-
B.
establishesRight
Indicates that one entity creates or confers a legal or formal entitlement or privilege upon another entity.
-
C.
majorAccessTown
Indicates that a location serves as a primary or significant access point to a town, such as a main route, gateway, or connection hub.
-
D.
authorityGranted
Indicates that one entity has formally given another entity the power, rights, or permission to act or make decisions, typically within a defined scope or context.
-
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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4562f48190831e959f5f309956 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.