Triple
T2389908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franco-Czechoslovak alliance |
E48916
|
entity |
| Predicate | diminishedBy |
P9925
|
FINISHED |
| Object | policy of appeasement |
—
|
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: policy of appeasement | Statement: [Franco-Czechoslovak alliance, diminishedBy, policy of appeasement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diminishedBy Context triple: [Franco-Czechoslovak alliance, diminishedBy, policy of appeasement]
-
A.
minimizedBy
Indicates that one entity serves to reduce, lessen, or make as small as possible the value, effect, or impact of another entity.
-
B.
reducedPowerOf
Indicates that one entity has a diminished or weakened level of power, authority, or effectiveness relative to another or to its previous state.
-
C.
reduces
chosen
Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
-
D.
hasDiminutive
Indicates that one entity is a diminutive form or smaller/affectionate variant of another entity.
-
E.
reducedCostOf
Indicates that one entity represents a lowered or discounted cost associated with another entity, typically compared to a standard or original price.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc7de1478819082238e8b8f88ed06 |
completed | March 7, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.