Triple
T31897167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish state |
E814314
|
entity |
| Predicate | lostSovereigntyDuring |
P76678
|
FINISHED |
| Object | Partitions of Poland |
—
|
NE NERFINISHED |
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: Partitions of Poland | Statement: [Polish state, lostSovereigntyDuring, Partitions of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostSovereigntyDuring Context triple: [Polish state, lostSovereigntyDuring, Partitions of Poland]
-
A.
lostSovereigntyIn
Indicates that an entity ceased to possess or exercise sovereign authority within a specified place or domain.
-
B.
lostSovereignty
chosen
Indicates that an entity has ceased to possess independent authority or control over its own governance or territory.
-
C.
historicalSovereigntyEndedBy
Indicates that a former sovereignty or ruling authority over an entity came to an end as a result of the specified event, action, or successor power.
-
D.
lostTerritoryBy
Indicates that one entity has had control or ownership of a territory taken away by another entity.
-
E.
residualTerritoriesLostBy
Indicates that certain remaining or leftover territories were lost by a specified entity.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b165382c8190af1947dec907a015 |
completed | May 3, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:59 p.m.