Triple
T20733612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimmermann Telegram |
E509631
|
entity |
| Predicate | proposedActionByGermany |
P141299
|
FINISHED |
| Object | provide financial support to Mexico |
—
|
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: provide financial support to Mexico | Statement: [Zimmermann Telegram, proposedActionByGermany, provide financial support to Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedActionByGermany Context triple: [Zimmermann Telegram, proposedActionByGermany, provide financial support to Mexico]
-
A.
objectiveGermany
Indicates that an entity has Germany as its objective, target, or goal in a given context.
-
B.
MunichAgreementSignatory
Indicates that an entity was a formal signatory to the Munich Agreement.
-
C.
PrussianObjective
Indicates that an entity has the goal, target, or strategic objective of achieving or advancing something specifically related to Prussia or Prussian interests.
-
D.
strategicGoalOfGermany
Indicates that something is a strategic goal or long-term objective pursued by Germany.
-
E.
strategyUsedByGermany
Indicates that a particular strategy is one that was employed or adopted by Germany.
- F. None of above. chosen
Provenance (4 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1ef3040819085c8056e75571104 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:31 p.m.