Triple
T30069093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calenberg line |
E764124
|
entity |
| Predicate | elevatedToKingdom |
P112164
|
FINISHED |
| Object | 1814 |
—
|
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: 1814 | Statement: [Calenberg line, elevatedToKingdom, 1814]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToKingdom Context triple: [Calenberg line, elevatedToKingdom, 1814]
-
A.
elevatedToKingdomBy
Indicates that one entity raised or promoted another entity to the status or rank of a kingdom.
-
B.
elevationToKingdom
chosen
Indicates the act or process by which an entity is raised in status or rank to become a kingdom.
-
C.
elevatedToDukedom
Indicates that an entity has been raised or promoted to the rank or title of a dukedom.
-
D.
elevatedToDuchy
Indicates that a territory, region, or domain has been formally raised in rank or status to become a duchy.
-
E.
elevatedToPrincipalityBy
Indicates that an entity was raised in status or rank to a principality by another entity or authority.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 7 p.m.