Triple
T14000804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Principality of Hohenzollern-Sigmaringen |
E336814
|
entity |
| Predicate | annexationEffective |
P43098
|
FINISHED |
| Object | 1850 |
—
|
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: 1850 | Statement: [Principality of Hohenzollern-Sigmaringen, annexationEffective, 1850]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: annexationEffective Context triple: [Principality of Hohenzollern-Sigmaringen, annexationEffective, 1850]
-
A.
annexationInstrument
Indicates the legal or formal instrument (such as a treaty, decree, or law) by which one entity annexes or incorporates another.
-
B.
annexationPolicy
Indicates a policy or practice of formally incorporating one territory into the jurisdiction or sovereignty of another.
-
C.
annexationBasis
Indicates the legal, political, or historical grounds used to justify the annexation of one territory by another.
-
D.
annex
Indicates the act of formally incorporating one entity, typically a territory, into the domain or control of another.
-
E.
annexedDuring
chosen
Indicates that one entity was formally incorporated into and brought under the control of another entity during a specified time period.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2eb81b208190a961e49a02fa4140 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.