Triple
T257580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Scotland |
E5468
|
entity |
| Predicate | dynasticUnionStartDate |
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: [Kingdom of Scotland, dynasticUnionStartDate, 1603]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticUnionStartDate Context triple: [Kingdom of Scotland, dynasticUnionStartDate, 1603]
-
A.
dateOfUnionFormation
chosen
Indicates the date on which a union was formally established or came into existence.
-
B.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
C.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
D.
conquestYear
Indicates the year in which one entity successfully conquered or took control over another entity.
-
E.
dominantDynasty
Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d703e688190bb86c69527e306f5 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b694c08819085bb4b256fa7736f |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.