Triple
T25403587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Gottorp |
E636490
|
entity |
| Predicate | hasDynasticClaim |
P7973
|
FINISHED |
| Object | Duchy of Holstein |
—
|
NE NERFINISHED |
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: Duchy of Holstein | Statement: [House of Gottorp, hasDynasticClaim, Duchy of Holstein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynasticClaim Context triple: [House of Gottorp, hasDynasticClaim, Duchy of Holstein]
-
A.
dynasticClaim
chosen
Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
-
B.
dynasticClaimBasis
Indicates the basis or grounds on which a person or lineage asserts a dynastic right or claim to rule.
-
C.
dynasticClaimants
Indicates a relationship where individuals or groups assert a hereditary right to a throne, title, or ruling position within a dynasty.
-
D.
isDynastic
Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
-
E.
hasDynasticConnections
Indicates that one entity is related to another through familial or hereditary ties between ruling or noble dynasties.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584fcac20819093a4919df2ef23b6 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:52 p.m.