Triple
T151668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chamberlain government |
E3443
|
entity |
| Predicate | dateOfMunichAgreement |
P2503
|
FINISHED |
| Object | 1938-09-30 |
—
|
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: 1938-09-30 | Statement: [Chamberlain government, dateOfMunichAgreement, 1938-09-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfMunichAgreement Context triple: [Chamberlain government, dateOfMunichAgreement, 1938-09-30]
-
A.
treatyDate
chosen
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
B.
dateOfUnionFormation
Indicates the date on which a union was formally established or came into existence.
-
C.
invasionDate
Indicates the date on which an invasion event occurred or began.
-
D.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
E.
dateOfBrexit
Indicates the specific calendar date on which Brexit (the United Kingdom’s withdrawal from the European Union) formally took place.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580f55a88190b37b54ee0ed5ac7c |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a2565adaf48190b68ae4444ff83ccd |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.