Triple
T22236109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Medal |
E549596
|
entity |
| Predicate | mayBeWornWith |
P27860
|
FINISHED |
| Object | national military decorations |
—
|
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: national military decorations | Statement: [NATO Medal, mayBeWornWith, national military decorations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeWornWith Context triple: [NATO Medal, mayBeWornWith, national military decorations]
-
A.
mayBeWorn
Indicates that one entity is suitable or allowed to be worn by another entity, typically as clothing, accessories, or adornment.
-
B.
typicallyWornWith
chosen
Indicates that one item of clothing or accessory is commonly or customarily worn together with another.
-
C.
notWornWith
Indicates that one item is not worn at the same time as another item, implying mutual exclusivity in being worn together.
-
D.
alsoWornIn
Indicates that an item of clothing or accessory is additionally worn in another context, location, or time beyond the primary one mentioned.
-
E.
wornAs
Indicates that one entity is used or put on as clothing, an accessory, or a wearable item by another entity.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf7b1d8819091087dcfdb2e967c |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.