Triple
T3721395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-Standartenführer |
E81644
|
entity |
| Predicate | woreOnCollar |
P43568
|
FINISHED |
| Object | three oak leaves insignia |
—
|
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: three oak leaves insignia | Statement: [SS-Standartenführer, woreOnCollar, three oak leaves insignia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: woreOnCollar Context triple: [SS-Standartenführer, woreOnCollar, three oak leaves insignia]
-
A.
collarFeature
chosen
Indicates that one entity has a specific characteristic, detail, or attribute related to a collar.
-
B.
supporterCollar
Indicates that one entity serves as a collar-like structural element that supports or stabilizes another entity.
-
C.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
D.
neckCharacteristic
Indicates that an entity has a specific attribute, feature, or quality related to its neck.
-
E.
wornAround
Indicates that one entity is physically worn encircling or surrounding another entity (e.g., around a body part or object).
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca9d29208190bbf38a6aa88f954a |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.