Triple
T5291532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander with Star |
E119751
|
entity |
| Predicate | insigniaReverse |
P21497
|
FINISHED |
| Object | monogram of the reigning Norwegian monarch |
—
|
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: monogram of the reigning Norwegian monarch | Statement: [Commander with Star, insigniaReverse, monogram of the reigning Norwegian monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insigniaReverse Context triple: [Commander with Star, insigniaReverse, monogram of the reigning Norwegian monarch]
-
A.
insigniaName
Indicates the specific name or designation assigned to an insignia associated with an entity.
-
B.
insigniaCaption
Indicates the text that serves as a caption or explanatory label specifically for an insignia.
-
C.
insigniaUsedFor
Indicates that a particular insignia is employed or designated for a specific purpose, function, or use.
-
D.
symbolOnInsignia
chosen
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
E.
insigniaColorContext
Indicates the contextual circumstances or conditions under which a particular insignia color is used or holds its specific meaning.
- 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.