Triple
T31606608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanover |
E806505
|
entity |
| Predicate | personalUnionEnd |
P86182
|
FINISHED |
| Object | 1837 |
—
|
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: 1837 | Statement: [Hanover, personalUnionEnd, 1837]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalUnionEnd Context triple: [Hanover, personalUnionEnd, 1837]
-
A.
personalUnionResult
Indicates that a personal union between entities has occurred and specifies the resulting combined political or dynastic arrangement.
-
B.
relationshipEnd
chosen
Indicates that a previously existing relationship between entities has been terminated or has come to an end.
-
C.
personalUnionPeriod
Indicates a time span during which two or more distinct political entities are joined under a single ruler in a personal union.
-
D.
partnerInUnionWith
Indicates a mutual partnership or union relationship between two entities, such as a civil, domestic, or similar legally or socially recognized union.
-
E.
formedPersonalUnionWith
Indicates that one entity has entered into a close, unified personal relationship or alliance with another entity, often implying a merger of roles, identities, or interests.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a87033148190a434c60c1f1191d8 |
completed | May 3, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:35 p.m.