Triple
T7758038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pictland |
E175946
|
entity |
| Predicate | unificationLedTo |
P78544
|
FINISHED |
| Object | formation of the Kingdom of Alba |
—
|
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: formation of the Kingdom of Alba | Statement: [Pictland, unificationLedTo, formation of the Kingdom of Alba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unificationLedTo Context triple: [Pictland, unificationLedTo, formation of the Kingdom of Alba]
-
A.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
B.
aimedToUnify
Indicates an intention or effort by one entity to bring multiple entities, groups, or elements together into a single unified whole.
-
C.
unificationAct
Indicates the formal joining or merging of previously separate entities into a single unified whole.
-
D.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
E.
historicalPeriodOfUnification
Indicates the historical time span during which separate entities were unified into a single political or organizational whole.
- F. None of above. chosen
Provenance (4 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_69c6996180088190832e38e8d83ff54a |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c70524c3948190a163dc5f4ecdffa7 |
completed | March 27, 2026, 10:31 p.m. |
Created at: March 27, 2026, 4:09 p.m.