Triple
T1017941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stewart family |
E21973
|
entity |
| Predicate | unionOfCrownsYear |
P3470
|
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: [Stewart family, unionOfCrownsYear, 1603]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionOfCrownsYear Context triple: [Stewart family, unionOfCrownsYear, 1603]
-
A.
crownUnionWith
Indicates the formal unification of two or more political entities under a single crown or sovereign authority.
-
B.
royalDesignationYear
Indicates the year in which an entity was formally granted or recognized with a royal status or designation.
-
C.
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.
-
D.
dynasticUnionStartEvent
Indicates the event marking the beginning of a dynastic union, where two ruling houses or dynasties become joined under a shared rule or arrangement.
-
E.
dateOfUnionFormation
chosen
Indicates the date on which a union was formally established or came into existence.
- 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_69a493c68e24819080ed0ee8bcfd5ce0 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c4d488819081d8214ba0a22fe5 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.