Triple
T22616596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish royal family |
E558163
|
entity |
| Predicate | unionOfCrowns |
P11440
|
FINISHED |
| Object | 1603 |
—
|
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: 1603 | Statement: [Scottish royal family, unionOfCrowns, 1603]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionOfCrowns Context triple: [Scottish royal family, unionOfCrowns, 1603]
-
A.
crownUnionWith
chosen
Indicates the formal unification of two or more political entities under a single crown or sovereign authority.
-
B.
dynasticUnion
Indicates a political relationship in which two or more distinct states are ruled by the same dynasty or monarch while formally remaining separate entities.
-
C.
hasConsortCrowned
Indicates that an individual has a spouse or consort who has been formally crowned, typically in a royal or ceremonial context.
-
D.
royalAssociation
Indicates a relationship in which an entity is connected or linked to royalty, a royal person, or a royal institution.
-
E.
spouseOfHeirToThrone
Indicates that one person is the married partner of an individual who is the heir to a throne.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f167eeb220819082c90a8bd3cadc4c |
completed | April 29, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:59 p.m.