Triple
T28601083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Great Britain (Jacobite claim) |
E723912
|
entity |
| Predicate | claimedByDynasty |
P7973
|
FINISHED |
| Object | exiled Stuart line |
—
|
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: exiled Stuart line | Statement: [Kingdom of Great Britain (Jacobite claim), claimedByDynasty, exiled Stuart line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedByDynasty Context triple: [Kingdom of Great Britain (Jacobite claim), claimedByDynasty, exiled Stuart line]
-
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.
heldUnderDynasty
Indicates that an entity’s position, title, or authority was exercised during the rule of a specific dynasty.
-
D.
reignClaim
Indicates a claim or assertion by an entity that it has the right to rule or hold sovereign authority over a domain or people.
-
E.
kingdomClaimed
Indicates that an entity has asserted ownership, control, or sovereign authority over a particular kingdom.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 4:24 a.m.