Triple
T702081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syrian–Lebanese campaign |
E14019
|
entity |
| Predicate | dateOfArmistice |
P18436
|
FINISHED |
| Object | 1941-07-14 |
—
|
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: 1941-07-14 | Statement: [Syrian–Lebanese campaign, dateOfArmistice, 1941-07-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfArmistice Context triple: [Syrian–Lebanese campaign, dateOfArmistice, 1941-07-14]
-
A.
armisticeSignedWith
Indicates that a formal agreement to stop fighting (an armistice) has been concluded between the two related parties.
-
B.
warEndDate
Indicates the date on which a particular war or armed conflict officially ended.
-
C.
lastWarEnd
Indicates that a specified war or conflict has reached its conclusion at a particular time or event.
-
D.
ItalyArmisticeDate
Indicates the date on which an armistice involving Italy was formally agreed or came into effect.
-
E.
dateOfWarDeclarationOnGermany
Indicates the specific date on which a formal declaration of war was made against Germany.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a544e3608190ac315c7aa9f88e7e |
completed | March 1, 2026, 8:44 p.m. |
| PD | Predicate disambiguation | batch_69a4a4ec8c748190b198492a0eea4445 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a54235548190b46218ea18f77341 |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:36 p.m.