Triple
T301080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Axis |
E6198
|
entity |
| Predicate | AntiCominternPactSigned |
P2503
|
FINISHED |
| Object | 25 November 1936 |
—
|
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: 25 November 1936 | Statement: [Axis, AntiCominternPactSigned, 25 November 1936]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AntiCominternPactSigned Context triple: [Axis, AntiCominternPactSigned, 25 November 1936]
-
A.
armisticeSignedWith
Indicates that a formal agreement to stop fighting (an armistice) has been concluded between the two related parties.
-
B.
peaceTreatySigned
Indicates that a formal peace treaty has been concluded and signed between previously opposing parties, establishing agreed terms to end or prevent conflict.
-
C.
treatySignedPlace
Indicates the location where a treaty was formally signed or concluded.
-
D.
partnerInTreaty
Indicates that an entity is a formal participant or signatory in a specific treaty or international agreement.
-
E.
treatyDate
chosen
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea2fba548190a5aeb1597dca96bd |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93aff048190a633c8ae2b76a41f |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.