Triple
T32582721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Cross of the Order of Leopold |
E832832
|
entity |
| Predicate | hasWearingMode |
P14609
|
FINISHED |
| Object | sash worn over the shoulder |
—
|
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: sash worn over the shoulder | Statement: [Grand Cross of the Order of Leopold, hasWearingMode, sash worn over the shoulder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWearingMode Context triple: [Grand Cross of the Order of Leopold, hasWearingMode, sash worn over the shoulder]
-
A.
mayBeWorn
Indicates that one entity is suitable or allowed to be worn by another entity, typically as clothing, accessories, or adornment.
-
B.
wearerStatus
Indicates the condition or role of an entity in its capacity as a wearer of something (e.g., clothing, equipment, or an accessory).
-
C.
wearingMethod
chosen
Indicates the manner or method by which something is worn or put on.
-
D.
hasIntendedWearer
Indicates that an item is associated with the person or entity it is meant or designed to be worn by.
-
E.
wearingForm
Indicates that one entity is dressed in or has on a particular form of clothing, outfit, or wearable item.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:04 a.m.