Triple
T8896953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sceptre with the Cross |
E211826
|
entity |
| Predicate | positionInRegalia |
P85122
|
FINISHED |
| Object | principal sceptre of the sovereign |
—
|
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: principal sceptre of the sovereign | Statement: [Sceptre with the Cross, positionInRegalia, principal sceptre of the sovereign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInRegalia Context triple: [Sceptre with the Cross, positionInRegalia, principal sceptre of the sovereign]
-
A.
positionOnMonarchy
Indicates a stance, opinion, or policy position that an entity holds regarding the institution or system of monarchy.
-
B.
positionInRoyalFamily
Indicates the familial rank or role an individual holds within a royal family hierarchy.
-
C.
positionInDynasty
Indicates the specific role or rank an individual holds within a particular dynasty’s internal hierarchy.
-
D.
positionDuringCoronation
Indicates the specific role, title, or office an entity held at the time of a coronation event.
-
E.
positionOfEmblem
Indicates the spatial placement or location of an emblem relative to a reference object or surface.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6424a8c08190aef2aa2079dd85f1 |
completed | April 1, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2bfb38819083d5eb1af8ccf4d6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:54 p.m.