Triple
T19022256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linköping Bloodbath |
E465514
|
entity |
| Predicate | numberOfExecuted |
P19112
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Linköping Bloodbath, numberOfExecuted, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfExecuted Context triple: [Linköping Bloodbath, numberOfExecuted, 5]
-
A.
numberOfExecutions
chosen
Indicates the count of times a particular action, process, or event has been carried out.
-
B.
numberOfMembersExecuted
Indicates the count of members within a group or organization who have been put to death, typically as a result of an official or authoritative decision.
-
C.
executedFor
Indicates that one entity carried out an action, task, or operation on behalf of or in fulfillment of an obligation to another entity.
-
D.
numberOfTests
Indicates the quantity of tests associated with or performed in a given context or entity.
-
E.
executedWith
Indicates that an action or process was carried out using, accompanied by, or in conjunction with a specified tool, method, or participant.
- 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_69d8dd025c188190a1d81f5b4ec7e2c6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d6dfa3c88190a057c3385d680cf8 |
completed | April 20, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69e4a2fd80c081908237317a3a883e1c |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.