Triple
T17353300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Befehlstaktik |
E421865
|
entity |
| Predicate | tendsToProduce |
P45631
|
FINISHED |
| Object | rigid operational behavior |
—
|
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: rigid operational behavior | Statement: [Befehlstaktik, tendsToProduce, rigid operational behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tendsToProduce Context triple: [Befehlstaktik, tendsToProduce, rigid operational behavior]
-
A.
produces
Indicates that one entity creates, generates, or yields another entity as a result or output.
-
B.
increasesProductionOf
Indicates that one entity causes a rise or enhancement in the amount or rate at which another entity is produced.
-
C.
isFrequentlyProducedBy
Indicates that something is commonly or regularly generated, created, or brought about by a particular entity or source.
-
D.
producesFor
Indicates that one entity creates, manufactures, or generates something specifically intended for another entity’s use, benefit, or distribution.
-
E.
helpsProduce
chosen
Indicates that one entity contributes to or facilitates the creation, generation, or production of 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a2e660c81908700aed5c42e9043 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.