Triple
T30620463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remembrance Day (United Kingdom) |
E779431
|
entity |
| Predicate | armisticeTime |
P169630
|
FINISHED |
| Object | 11: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: 11:00 | Statement: [Remembrance Day (United Kingdom), armisticeTime, 11:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armisticeTime Context triple: [Remembrance Day (United Kingdom), armisticeTime, 11:00]
-
A.
armisticeSignedAt
Indicates the specific place where an armistice agreement was formally signed.
-
B.
dateOfArmistice
Indicates the specific calendar date on which an armistice agreement between parties took effect.
-
C.
armisticeSignedYear
Indicates the year in which an armistice agreement was formally signed between the involved parties.
-
D.
armisticeSignedWith
Indicates that a formal agreement to stop fighting (an armistice) has been concluded between the two related parties.
-
E.
hasArmistice
Indicates a formal agreement between opposing parties to stop active hostilities, typically marking a ceasefire or suspension of fighting.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689ee11988190a25cbd9b9fad6ec3 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 29, 2026, 8:27 p.m.