Triple
T377185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Vith |
E8397
|
entity |
| Predicate | changedSovereignty |
P1701
|
FINISHED |
| Object | Prussia in the 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: Prussia in the 19th century | Statement: [St. Vith, changedSovereignty, Prussia in the 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedSovereignty Context triple: [St. Vith, changedSovereignty, Prussia in the 19th century]
-
A.
territorialChange
chosen
Indicates a change in control or ownership of geographic territory from one entity to another, often as a result of political, legal, or military events.
-
B.
formerSovereign
Indicates that an entity once held sovereign (ruling) authority over another entity but no longer does.
-
C.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
D.
changesAllianceOf
Indicates that one entity causes or initiates a change in the alliance or affiliation status of another entity.
-
E.
sovereignClaimedBy
Indicates that a territory or entity is asserted to be under the sovereignty or ultimate authority of a particular claimant.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec1804108190a1e94526b71289ea |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96351cc8190a55adf95f8c27e9e |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.