Triple
T37188348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radzionków |
E921380
|
entity |
| Predicate | lostMunicipalRightsIn |
P157543
|
FINISHED |
| Object | 1975 |
—
|
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: 1975 | Statement: [Radzionków, lostMunicipalRightsIn, 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostMunicipalRightsIn Context triple: [Radzionków, lostMunicipalRightsIn, 1975]
-
A.
lostFeudalRightsBy
Indicates that one party ceased to hold feudal rights or privileges as a result of actions or circumstances attributable to another party.
-
B.
lostRightsBy
Indicates that one entity has had certain rights removed, revoked, or forfeited as a result of actions or circumstances involving another entity.
-
C.
lostTownRights
chosen
Indicates that a settlement or locality has had its official town rights or municipal status revoked or removed.
-
D.
lostSovereigntyIn
Indicates that an entity ceased to possess or exercise sovereign authority within a specified place or domain.
-
E.
formerMunicipalityDisestablished
Indicates that a municipality, which previously existed as an administrative unit, was officially dissolved or ceased to exist at a specific point in time.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.