Triple
T115595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jallianwala Bagh massacre 1919 |
E2330
|
entity |
| Predicate | officialBritishInjured |
P4808
|
FINISHED |
| Object | over 1,000 |
—
|
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,000 | Statement: [Jallianwala Bagh massacre 1919, officialBritishInjured, over 1,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialBritishInjured Context triple: [Jallianwala Bagh massacre 1919, officialBritishInjured, over 1,000]
-
A.
casualtiesBritishWounded
chosen
Indicates the number of British individuals who were wounded as a result of a specific event or action.
-
B.
casualties
Indicates that an event, action, or situation resulted in people being killed or injured.
-
C.
casualtiesGermanWounded
Indicates that the relationship specifies the number of German individuals who were wounded (but not killed) as casualties in a particular event or context.
-
D.
hasInjuries
Indicates that an entity has sustained one or more physical or bodily injuries.
-
E.
casualtiesWoundedUS
Indicates that the relationship specifies the number of U.S. individuals who were wounded as casualties in 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a256456d908190b52c937fe6c4343f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.