Triple
T15222672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Note Crisis of 1961 |
E363799
|
entity |
| Predicate | typeOfPressure |
P33637
|
FINISHED |
| Object | diplomatic pressure |
—
|
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: diplomatic pressure | Statement: [Note Crisis of 1961, typeOfPressure, diplomatic pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPressure Context triple: [Note Crisis of 1961, typeOfPressure, diplomatic pressure]
-
A.
pressureType
chosen
Indicates the specific category or kind of pressure associated with an entity or interaction.
-
B.
typicalPressure
Indicates the usual or characteristic level of pressure typically associated with an entity, situation, or condition.
-
C.
pressureFrom
Indicates a relationship where one entity exerts influence, coercion, or force on another to affect its decisions, actions, or state.
-
D.
pressureRange
Indicates the range of pressure values within which a condition, process, or relationship is defined or valid.
-
E.
hasHumanPressure
Indicates that one entity exerts or experiences human-induced influence, stress, or impact in relation to another entity or environment.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00788b04881909dad9b346ce3b4a9 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.