Triple
T36825228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collar of the Order of the Sword |
E909991
|
entity |
| Predicate | wearingPosition |
P99826
|
FINISHED |
| Object | around the neck and shoulders |
—
|
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: around the neck and shoulders | Statement: [Collar of the Order of the Sword, wearingPosition, around the neck and shoulders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearingPosition Context triple: [Collar of the Order of the Sword, wearingPosition, around the neck and shoulders]
-
A.
wornPosition
chosen
Indicates the specific location or orientation on a body or object where an item is worn.
-
B.
wearingMethod
Indicates the manner or method by which something is worn or put on.
-
C.
wearingOrder
Indicates the relative sequence in which items are worn on or over one another (e.g., which garment is worn over or under another).
-
D.
areWornOn
Indicates that one entity is typically placed on and carried by another entity as an item of clothing or accessory.
-
E.
wearsOnBodyPart
Indicates that an entity places or has an item worn on a specific part of its body.
- 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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7ca9be7988190b200c5295bdc38c5 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.