Triple
T14570815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior Grand Warden |
E341905
|
entity |
| Predicate | ceremonialRegalia |
P80953
|
FINISHED |
| Object | jewel of office |
—
|
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: jewel of office | Statement: [Junior Grand Warden, ceremonialRegalia, jewel of office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialRegalia Context triple: [Junior Grand Warden, ceremonialRegalia, jewel of office]
-
A.
ceremonialDressFeature
Indicates that one entity is a characteristic, component, or distinguishing element of another entity’s ceremonial dress or attire.
-
B.
ceremonialSymbol
chosen
Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
-
C.
relatedRegalia
Indicates that there is an association or connection between items of regalia, such as ceremonial garments, insignia, or symbols of office.
-
D.
ceremonialAssociation
Indicates a relationship where entities are linked through participation in, role within, or connection to a formal ceremony or ritual event.
-
E.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f2121481908f2385637944785d |
completed | April 14, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.