Triple
T37419970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Mons (1691) |
E929822
|
entity |
| Predicate | garrisonSurrenderDate |
P4667
|
FINISHED |
| Object | 1691-04-08 |
—
|
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: 1691-04-08 | Statement: [Siege of Mons (1691), garrisonSurrenderDate, 1691-04-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonSurrenderDate Context triple: [Siege of Mons (1691), garrisonSurrenderDate, 1691-04-08]
-
A.
garrisonSurrenderedTo
Indicates that a defending military garrison formally capitulated and yielded control to another party.
-
B.
surrenderDate
chosen
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
C.
dateOfCityCapture
Indicates the specific date on which a city was taken or captured, typically in a military or political context.
-
D.
timeOfSurrender
Indicates the specific point in time at which an entity formally surrenders or yields.
-
E.
siegeEndDate
Indicates the date on which a siege concluded or was lifted.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.