Triple
T36309953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazi Party paramilitary ranks |
E894039
|
entity |
| Predicate | hierarchyPurpose |
P185121
|
FINISHED |
| Object | define chain of command |
—
|
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: define chain of command | Statement: [Nazi Party paramilitary ranks, hierarchyPurpose, define chain of command]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hierarchyPurpose Context triple: [Nazi Party paramilitary ranks, hierarchyPurpose, define chain of command]
-
A.
tagPurpose
Indicates the intended role, function, or use associated with a given tag in a particular context.
-
B.
accessPurpose
Indicates that one entity uses or accesses another entity specifically for a defined purpose or intended use.
-
C.
entryPurpose
Indicates the reason or intended use for which an entity is being entered, accessed, or recorded in a given context.
-
D.
separationPurpose
Indicates that one entity is separated from another with a specific intended purpose or reason for that separation.
-
E.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
- F. None of above. chosen
Provenance (4 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.