Triple
T32894326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Generalleutnant of the Waffen-SS |
E841423
|
entity |
| Predicate | approximateNATOCode |
P6062
|
FINISHED |
| Object | OF-7 |
—
|
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: OF-7 | Statement: [Generalleutnant of the Waffen-SS, approximateNATOCode, OF-7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateNATOCode Context triple: [Generalleutnant of the Waffen-SS, approximateNATOCode, OF-7]
-
A.
NATOcode
chosen
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
B.
natoEquivalent
Indicates that one entity is the counterpart or functional equivalent of another within the NATO (North Atlantic Treaty Organization) framework.
-
C.
natoNameInitialLetter
Indicates that one entity is the NATO phonetic alphabet code word corresponding to the initial letter of the other entity’s name.
-
D.
associatedWithNATO
Indicates a relationship in which an entity has a formal or recognized connection, affiliation, or involvement with NATO.
-
E.
NATOStandard
Indicates that something conforms to, is defined by, or is governed by standards established by NATO.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: May 1, 2026, 1:18 a.m.