Triple
T16243980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlos V |
E394321
|
entity |
| Predicate | monarchStyleClaimed |
P119623
|
FINISHED |
| Object | His Catholic Majesty |
—
|
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: His Catholic Majesty | Statement: [Carlos V, monarchStyleClaimed, His Catholic Majesty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchStyleClaimed Context triple: [Carlos V, monarchStyleClaimed, His Catholic Majesty]
-
A.
dynasticClaim
Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
-
B.
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.
-
C.
monarchSheIsHeirTo
Indicates that the subject is the designated heir to the specified monarch’s throne or title.
-
D.
dynasticClaimBasis
Indicates the basis or grounds on which a person or lineage asserts a dynastic right or claim to rule.
-
E.
isMonarchicalStyle
chosen
Indicates that the relationship or action involves having or using a monarchical style, such as a royal or sovereign form of address or title.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24560c6848190ae0e85ecb11a9264 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.