Triple
T4405341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Order of the Seraphim |
E93716
|
entity |
| Predicate | orderPrecedenceInSweden |
P56069
|
FINISHED |
| Object | first |
—
|
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: first | Statement: [Royal Order of the Seraphim, orderPrecedenceInSweden, first]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderPrecedenceInSweden Context triple: [Royal Order of the Seraphim, orderPrecedenceInSweden, first]
-
A.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
-
B.
orderPrecedenceInCanada
Indicates the relative legal or procedural priority that one item holds over another specifically within the Canadian context.
-
C.
wearingOrderPrecedenceInFinland
Indicates the prescribed priority or sequence in which items of clothing or regalia should be worn in Finland.
-
D.
orderPrecedenceWithinIndia
Indicates the relative ranking or priority of entities in terms of legal or administrative precedence within the jurisdiction of India.
-
E.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b35488d5b8819087370dd77249aefb |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3509997208190933f167f7e20ccfa |
completed | March 12, 2026, 11:47 p.m. |
Created at: March 12, 2026, 11:28 p.m.