Triple
T17713577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British declaration of war on Germany (1914) |
E441629
|
entity |
| Predicate | deadlineForUltimatum |
P79339
|
FINISHED |
| Object | 23:00 BST, 4 August 1914 |
—
|
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: 23:00 BST, 4 August 1914 | Statement: [British declaration of war on Germany (1914), deadlineForUltimatum, 23:00 BST, 4 August 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deadlineForUltimatum Context triple: [British declaration of war on Germany (1914), deadlineForUltimatum, 23:00 BST, 4 August 1914]
-
A.
dateOfUltimatum
Indicates the specific date on which an ultimatum was issued, delivered, or came into effect in the relationship between the involved parties.
-
B.
issuedUltimatumTo
Indicates that one entity has presented another entity with a final set of demands or conditions, often implying consequences if they are not accepted.
-
C.
notificationDeadline
chosen
Indicates the time or date by which a required notification must be sent or received.
-
D.
hasDeadline
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
E.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
- 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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4729cebd08190872be96a26d0f7ce |
completed | April 19, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69e3cde601d4819097903f471f1fe99a |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:06 a.m.