Triple

T532549
Position Surface form Disambiguated ID Type / Status
Subject Hunter Commission E12253 entity
Predicate concludedThat P16516 FINISHED
Object firing at Jallianwala Bagh was unjustified 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: firing at Jallianwala Bagh was unjustified | Statement: [Hunter Commission, concludedThat, firing at Jallianwala Bagh was unjustified]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: concludedThat
Context triple: [Hunter Commission, concludedThat, firing at Jallianwala Bagh was unjustified]
  • A. concluded
    Indicates that an entity has brought an event, process, discussion, or agreement to an end, often after reaching a decision or final judgment.
  • B. concludedBy
    Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
  • C. concludes
    Indicates that one entity brings something (such as an event, process, or discussion) to an end or reaches a final decision or judgment about it.
  • D. concludedAt
    Indicates the point in time at which an event, process, or relationship comes to an end or is completed.
  • E. typicalConclusion
    Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
  • 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_69a4933208e88190891f5debab1b776d completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4985e51908190a34aa82ea9dbee1e completed March 1, 2026, 7:49 p.m.
PD Predicate disambiguation batch_69a494b3e49081909810fa417b31306f completed March 1, 2026, 7:34 p.m.
PDg Predicate description generation batch_69a49857e1148190aa782b82675cf0b5 completed March 1, 2026, 7:49 p.m.
Created at: March 1, 2026, 7:32 p.m.