Triple
T842775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waffen-SS |
E18212
|
entity |
| Predicate | numberOfPersonnel |
P2307
|
FINISHED |
| Object | over 900000 at peak strength |
—
|
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: over 900000 at peak strength | Statement: [Waffen-SS, numberOfPersonnel, over 900000 at peak strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPersonnel Context triple: [Waffen-SS, numberOfPersonnel, over 900000 at peak strength]
-
A.
personnelComposition
Indicates the makeup or distribution of people or roles within a group, organization, or unit.
-
B.
numberOfPersons
chosen
Indicates the total count of individual persons associated with or involved in a given entity, event, or context.
-
C.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
D.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
E.
numberOfTroopsInvolved
Indicates the quantity of military personnel participating in or assigned to a specific operation, event, or engagement.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abe8a0bc81909b54af465e67be1f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7f396c8190aa8b8dfbe0b4f732 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.