Triple
T20686133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of the Military Cross (Poland) |
E508422
|
entity |
| Predicate | isWornOn |
P130852
|
FINISHED |
| Object | left side of the chest |
—
|
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: left side of the chest | Statement: [Order of the Military Cross (Poland), isWornOn, left side of the chest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWornOn Context triple: [Order of the Military Cross (Poland), isWornOn, left side of the chest]
-
A.
wearsOnBodyPart
chosen
Indicates that an entity places or has an item worn on a specific part of its body.
-
B.
wearClassification
Indicates a classification relationship specifying the type or category of wear associated with an entity or interaction.
-
C.
wornAround
Indicates that one entity is physically worn encircling or surrounding another entity (e.g., around a body part or object).
-
D.
wornAs
Indicates that one entity is used or put on as clothing, an accessory, or a wearable item by another entity.
-
E.
mayBeWorn
Indicates that one entity is suitable or allowed to be worn by another entity, typically as clothing, accessories, or adornment.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6beacc30081908e57cd7f2c3ef047 |
completed | April 21, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:45 a.m.