Triple
T1047477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Norwegian Order of St. Olav |
E22614
|
entity |
| Predicate | collarUsedOnOccasions |
P15655
|
FINISHED |
| Object | great state occasions |
—
|
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: great state occasions | Statement: [Royal Norwegian Order of St. Olav, collarUsedOnOccasions, great state occasions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collarUsedOnOccasions Context triple: [Royal Norwegian Order of St. Olav, collarUsedOnOccasions, great state occasions]
-
A.
wornAt
Indicates that an item is being worn on a specific part of the body or at a particular time or event.
-
B.
wornAs
Indicates that one entity is used or put on as clothing, an accessory, or a wearable item by another entity.
-
C.
wornFor
chosen
Indicates that an item is worn for a particular purpose, function, or occasion.
-
D.
wornAround
Indicates that one entity is physically worn encircling or surrounding another entity (e.g., around a body part or object).
-
E.
wornOver
Indicates that one item of clothing or accessory is positioned on top of and covering another item when worn.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f28c7c8190b9ca3749666bcbf3 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b72e3e488190b768005ad647886b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.