Triple
T25016105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowy Korczyn |
E626135
|
entity |
| Predicate | lostTownRights |
P157543
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Nowy Korczyn, lostTownRights, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostTownRights Context triple: [Nowy Korczyn, lostTownRights, 19th century]
-
A.
grantedTownRights
Indicates that an authority formally conferred municipal or town privileges and legal status upon a settlement.
-
B.
lostExclusiveRights
Indicates that an entity no longer holds previously exclusive legal or contractual rights to something, allowing others to obtain or exercise those rights.
-
C.
lostFeudalRightsBy
Indicates that one party ceased to hold feudal rights or privileges as a result of actions or circumstances attributable to another party.
-
D.
lostAuthorityOver
Indicates that an entity no longer holds control, power, or decision-making authority over another entity or domain it previously governed.
-
E.
lostSovereignty
Indicates that an entity has ceased to possess independent authority or control over its own governance or territory.
- F. None of above. chosen
Provenance (4 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_69e2ff27755881908490178e83701160 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44ba594a08190beb28ace68e1e120 |
completed | May 1, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:06 a.m.