Triple
T19425740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annexation of Hanover by Prussia |
E485974
|
entity |
| Predicate | statusOfHanoverBeforeEvent |
P135842
|
FINISHED |
| Object | independent kingdom |
—
|
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: independent kingdom | Statement: [Annexation of Hanover by Prussia, statusOfHanoverBeforeEvent, independent kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfHanoverBeforeEvent Context triple: [Annexation of Hanover by Prussia, statusOfHanoverBeforeEvent, independent kingdom]
-
A.
statusBefore1918
Indicates that a particular status, condition, or classification applied to an entity prior to the year 1918.
-
B.
legalStatusBefore1889
Indicates the legal status or condition that applied to an entity prior to the year 1889.
-
C.
startTimeOfRuleInHanover
Indicates the specific time at which a particular rule or regulation becomes effective or applicable within Hanover.
-
D.
functionDuringBonnCapitalEra
Indicates that a function, role, or activity occurred during the historical period when Bonn served as the capital.
-
E.
statusOfCityBeforeBattle
Indicates the condition or situation a city was in immediately prior to a specific battle.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63218772c8190a48b6cb01bd12b73 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.