Triple
T115599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jallianwala Bagh massacre 1919 |
E2330
|
entity |
| Predicate | roundsFiredEstimate |
P6156
|
FINISHED |
| Object | about 1,650 rounds |
—
|
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: about 1,650 rounds | Statement: [Jallianwala Bagh massacre 1919, roundsFiredEstimate, about 1,650 rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundsFiredEstimate Context triple: [Jallianwala Bagh massacre 1919, roundsFiredEstimate, about 1,650 rounds]
-
A.
numberOfRings
Indicates the quantity of rings associated with an entity.
-
B.
hasApproximateTotalSpeakers
Indicates that an entity is associated with an estimated or roughly calculated number of total speakers, rather than an exact count.
-
C.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
D.
estimatedStrength
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
E.
numberOfEvents
Indicates the quantity or count of events associated with a given entity or context.
- 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_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. |
| PDg | Predicate description generation | batch_69a2578329d08190be82e004b8224d2b |
completed | Feb. 28, 2026, 2:48 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.