Triple
T9562155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Messines (1917) |
E230699
|
entity |
| Predicate | mineDetonationDate |
P18902
|
FINISHED |
| Object | 1917-06-07 |
—
|
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: 1917-06-07 | Statement: [Battle of Messines (1917), mineDetonationDate, 1917-06-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineDetonationDate Context triple: [Battle of Messines (1917), mineDetonationDate, 1917-06-07]
-
A.
timeOfDetonation
chosen
Indicates the specific point in time at which a detonation event occurs.
-
B.
explosionDateApprox
Indicates that an explosion occurred on or around a specified date, where the exact date is not known or is only approximate.
-
C.
detonatedOver
Indicates that one entity caused an explosion or detonation to occur above or over another entity or location.
-
D.
detonatedBy
Indicates that an explosive or device is set off or caused to explode by a particular agent or entity.
-
E.
detonationPosition
Indicates the specific location or coordinates at which a detonation occurs or is intended to occur.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9965e7b881909df98e933db38092 |
completed | April 1, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.