Triple
T9562156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Messines (1917) |
E230699
|
entity |
| Predicate | mineCountApproximate |
P89801
|
FINISHED |
| Object | 19 mines detonated |
—
|
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: 19 mines detonated | Statement: [Battle of Messines (1917), mineCountApproximate, 19 mines detonated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineCountApproximate Context triple: [Battle of Messines (1917), mineCountApproximate, 19 mines detonated]
-
A.
junctionCountApprox
Indicates an approximate count of junctions or connection points involved in or associated with the given entities.
-
B.
approximateNumberOfIslands
Indicates an estimated or rough count of how many islands are present or associated with a given context.
-
C.
sectionCountApproximate
Indicates that the number of sections associated with an entity is known only approximately rather than as an exact count.
-
D.
hasApproximateBrickCount
Indicates that an entity is associated with an estimated or non-exact number of bricks.
-
E.
hasApproximateIslandsCount
Indicates that an entity is associated with an estimated or non-exact number of islands.
- 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_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. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:03 p.m.