Triple
T11729875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Charles XIII |
E278869
|
entity |
| Predicate | orderOfPrecedenceInSweden |
P56069
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Order of Charles XIII, orderOfPrecedenceInSweden, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderOfPrecedenceInSweden Context triple: [Order of Charles XIII, orderOfPrecedenceInSweden, high]
-
A.
orderPrecedenceInSweden
chosen
Indicates the hierarchical ranking or protocol precedence between entities within the Swedish order of precedence system.
-
B.
orderPrecedenceInDenmark
Indicates that one entity holds a higher or lower formal rank or protocol priority than another within the Danish order of precedence.
-
C.
wearingOrderPrecedenceInFinland
Indicates the prescribed priority or sequence in which items of clothing or regalia should be worn in Finland.
-
D.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
-
E.
precedenceInScotland
Indicates that one entity holds a higher or lower formal rank, status, or ceremonial priority than another within the Scottish order of precedence.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d80ef881908cab956787ab07fd |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.