Triple
T29850787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-Gruppenführer |
E758062
|
entity |
| Predicate | wornOnUniformAs |
P55523
|
FINISHED |
| Object | three oak leaves collar patch |
—
|
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 collar patch | Statement: [SS-Gruppenführer, wornOnUniformAs, three oak leaves collar patch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wornOnUniformAs Context triple: [SS-Gruppenführer, wornOnUniformAs, three oak leaves collar patch]
-
A.
wearsInsigniaAt
Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
-
B.
wearsOnUniform
Indicates that an item is part of and is worn as a component of a uniform.
-
C.
woreUniformOf
Indicates that one entity was dressed in or used the official uniform associated with another entity (such as an organization, group, or role).
-
D.
rankInsigniaWornOn
chosen
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
-
E.
wearsUniformSimilarTo
Indicates that one entity wears a uniform that is similar in appearance or style to the uniform worn 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67647d9f881908567463e1b38d70f |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:44 p.m.