Triple
T36416046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | collar of the Order of the Seraphim |
E897005
|
entity |
| Predicate | rankOfOrder |
P152574
|
FINISHED |
| Object | highest Swedish order of chivalry |
—
|
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: highest Swedish order of chivalry | Statement: [collar of the Order of the Seraphim, rankOfOrder, highest Swedish order of chivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankOfOrder Context triple: [collar of the Order of the Seraphim, rankOfOrder, highest Swedish order of chivalry]
-
A.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
B.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
C.
rankIn
chosen
Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
-
D.
rankIndicated
Indicates that one entity specifies, denotes, or reveals the hierarchical rank or level of another entity.
-
E.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.