Triple
T30884976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Preußisch Holland |
E786733
|
entity |
| Predicate | changedSovereigntyTo |
P124980
|
FINISHED |
| Object | Polen |
—
|
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: Polen | Statement: [Preußisch Holland, changedSovereigntyTo, Polen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedSovereigntyTo Context triple: [Preußisch Holland, changedSovereigntyTo, Polen]
-
A.
replacedRegimeOf
Indicates that one regime has taken the place of or succeeded another regime in power or authority.
-
B.
replacedPreviousRegimeOf
Indicates that one regime took over and succeeded another regime, effectively displacing it from power.
-
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.
wasKingdomUntil
Indicates that an entity functioned as a kingdom governing another entity up to a specified end time or event.
-
E.
hasTerritoryReorganizedInto
chosen
Indicates that an entity’s territorial boundaries or administrative divisions have been restructured to form another specified territory.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:49 p.m.