Triple
T3160297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polnische Polizei im Generalgouvernement |
E66084
|
entity |
| Predicate | tookOrdersFrom |
P17822
|
FINISHED |
| Object | German police commanders |
—
|
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: German police commanders | Statement: [Polnische Polizei im Generalgouvernement, tookOrdersFrom, German police commanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookOrdersFrom Context triple: [Polnische Polizei im Generalgouvernement, tookOrdersFrom, German police commanders]
-
A.
canOrder
Indicates that one entity has the ability or permission to place an order for another entity or item.
-
B.
recognizesOrders
chosen
Indicates that one entity formally acknowledges and accepts the orders or directives issued by another entity.
-
C.
leadsOrder
Indicates that one entity holds primary responsibility or authority over the order associated with another entity.
-
D.
entersOrderThrough
Indicates that one party places or submits an order by means of, or via the involvement of, another party or system.
-
E.
orderFoundedFrom
Indicates that an order was initiated or created as a result of, or originating from, a specific source or prior 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada61606bc8190a8ad760d680924eb |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfe0a948190928f2201d671c654 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.