Triple
T554628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James VI and I |
E11914
|
entity |
| Predicate | politicalConcept |
P12806
|
FINISHED |
| Object | divine right of kings |
—
|
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: divine right of kings | Statement: [James VI and I, politicalConcept, divine right of kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalConcept Context triple: [James VI and I, politicalConcept, divine right of kings]
-
A.
politicalConceptAssociated
chosen
Indicates that there is a conceptual or thematic association between a political concept and another entity (such as an idea, event, policy, or actor).
-
B.
ideology
Indicates the belief system or set of political, social, or philosophical principles that an entity adheres to or promotes.
-
C.
philosophicalConcept
Indicates that one entity is a philosophical concept that characterizes, explains, or is thematically central to the other entity.
-
D.
ideologicalGoal
Indicates that an entity aims to promote, realize, or advance a particular ideology or set of ideological principles.
-
E.
ideologyComponent
Indicates that one ideology is a constituent or defining part of another, broader ideology.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991c524481908b2bb88c4feabec6 |
completed | March 1, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.