Triple
T17353289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Befehlstaktik |
E421865
|
entity |
| Predicate | isOftenCriticizedFor |
P805
|
FINISHED |
| Object | inflexibility |
—
|
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: inflexibility | Statement: [Befehlstaktik, isOftenCriticizedFor, inflexibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenCriticizedFor Context triple: [Befehlstaktik, isOftenCriticizedFor, inflexibility]
-
A.
criticizedFor
chosen
Indicates that one entity expresses disapproval or negative judgment of another entity specifically because of a particular action, quality, or outcome.
-
B.
sometimesCriticizedFor
Indicates that an entity is on occasion the target of criticism for a particular reason, behavior, or attribute.
-
C.
hasCriticism
Indicates that one entity expresses disapproval, objection, or negative evaluation directed toward another entity.
-
D.
aimsToCritique
Indicates an intention to analyze and point out faults, limitations, or weaknesses in something.
-
E.
criticizedConstruct
Indicates that one entity expressed disapproval or negative judgment about another entity’s constructed work, idea, or creation.
- 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.