Triple

T35412191
Position Surface form Disambiguated ID Type / Status
Subject Riverfront Coliseum E1023540 entity
Predicate consequenceOf1979Incident P187605 FINISHED
Object changes in crowd control policies 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: changes in crowd control policies | Statement: [Riverfront Coliseum, consequenceOf1979Incident, changes in crowd control policies]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: consequenceOf1979Incident
Context triple: [Riverfront Coliseum, consequenceOf1979Incident, changes in crowd control policies]
  • A. significantEventConsequence
    Indicates that one event leads to an important or impactful consequence for another event, state, or entity.
  • B. consequenceOfAssassinationAttempt
    Indicates a state, event, or condition that occurs as a direct result of an assassination attempt.
  • C. unexpectedConsequenceOf
    Indicates that one event, action, or condition occurs as an unforeseen or unintended result of another.
  • D. K-219IncidentOutcome
    Indicates the resulting consequences, resolutions, or status changes that occurred as a direct outcome of the K-219 incident.
  • E. consequenceInText
    Indicates that one event, action, or state is presented in the text as a consequence or result of another.
  • 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_69f76df54bac8190bd0d3b0eb35cda5f completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
PDg Predicate description generation batch_69fb6fdab95c81909acff3c6a2359787 completed May 6, 2026, 4:44 p.m.
Created at: May 3, 2026, 4:03 p.m.