Triple
T32578831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Hanover |
E832722
|
entity |
| Predicate | lostIndependenceIn |
P174615
|
FINISHED |
| Object | 1866 |
—
|
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: 1866 | Statement: [Kingdom of Hanover, lostIndependenceIn, 1866]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostIndependenceIn Context triple: [Kingdom of Hanover, lostIndependenceIn, 1866]
-
A.
achievedIndependenceFrom
Indicates that one entity has successfully gained political or organizational independence from another entity that previously held control or authority over it.
-
B.
independenceRestored
Indicates that a previously dependent or controlled entity has regained its autonomy or self-governance.
-
C.
gainedIndependenceThrough
Indicates that an entity achieved its independence by means of, or as a result of, a specified process, event, agreement, or struggle.
-
D.
gainedIndependenceAs
Indicates that an entity achieved political or administrative independence in the specific form, status, or identity denoted by another entity.
-
E.
soughtIndependenceFrom
Indicates that one entity actively pursued political or organizational separation and autonomy from another entity.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c667f4a881908bf678f99f056a0c |
completed | May 3, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c2df27ec8190912ec8eb488836d0 |
completed | May 3, 2026, 3:37 a.m. |
Created at: May 1, 2026, 1:04 a.m.