Triple
T769740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armistice of 11 November 1918 |
E16254
|
entity |
| Predicate | cameIntoEffectAt |
P1260
|
FINISHED |
| Object | 1918-11-11T11:00:00 |
—
|
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: 1918-11-11T11:00:00 | Statement: [Armistice of 11 November 1918, cameIntoEffectAt, 1918-11-11T11:00:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoEffectAt Context triple: [Armistice of 11 November 1918, cameIntoEffectAt, 1918-11-11T11:00:00]
-
A.
cameIntoForceInYear
Indicates that a law, agreement, or formal measure became legally effective or operational in a specified calendar year.
-
B.
cameIntoEffectInDecade
Indicates that something (such as a law, policy, or agreement) officially began to be in force during a specified decade.
-
C.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
D.
enactedAfter
Indicates that one enactment event occurred later in time than another enactment event.
-
E.
dateEnacted
chosen
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a70376988190be2826259f5281ab |
completed | March 1, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69a4a508c42c8190850a0ac7844a3ea9 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.