Triple
T21052872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Visby (1361) |
E518632
|
entity |
| Predicate | estimatedDead |
P661
|
FINISHED |
| Object | over 1,800 Gotlandic defenders |
—
|
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: over 1,800 Gotlandic defenders | Statement: [Battle of Visby (1361), estimatedDead, over 1,800 Gotlandic defenders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedDead Context triple: [Battle of Visby (1361), estimatedDead, over 1,800 Gotlandic defenders]
-
A.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
B.
estimatedUsing
Indicates that one entity’s value, state, or outcome is derived by applying an estimation method, model, or procedure based on another entity.
-
C.
possiblyDiedIn
Indicates that an entity is believed or suspected to have died in a particular place, but this is uncertain or not definitively confirmed.
-
D.
deathStatus
Indicates whether an entity is alive, dead, or in another specified state related to mortality.
-
E.
casualtiesEstimate
chosen
Indicates an estimated number of people killed, injured, or otherwise harmed as a result of an event or incident.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7cabe881909e6b258a14d501a6 |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:35 p.m.