Triple

T37860213
Position Surface form Disambiguated ID Type / Status
Subject Total Revolution E944304 entity
Predicate seeksChangeThrough P28300 FINISHED
Object mass civil disobedience 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: mass civil disobedience | Statement: [Total Revolution, seeksChangeThrough, mass civil disobedience]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: seeksChangeThrough
Context triple: [Total Revolution, seeksChangeThrough, mass civil disobedience]
  • A. changesEvery
    Indicates that one entity undergoes a change whenever or each time another specified condition, event, or entity changes.
  • B. seeksStatusChange chosen
    Indicates an entity’s intention or attempt to alter the current state, condition, or status of another entity or situation.
  • C. changesWith
    Indicates that one entity varies or is modified in response to changes in another entity.
  • D. changesMindAfter
    Indicates that one entity revises or reverses a previously held decision, opinion, or intention after another entity’s action, statement, or influence.
  • E. canChangeIn
    Indicates that one entity is capable of undergoing alteration, transformation, or variation within the context or influence of another entity or condition.
  • 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_69f76eee2f9c8190b1272aa2ee55ebf5 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbbae559a8819086ef839973f8d9b2 completed May 6, 2026, 10:04 p.m.
PD Predicate disambiguation batch_69fbb1440fa08190abf25ba684f75b6e completed May 6, 2026, 9:23 p.m.
Created at: May 3, 2026, 4:19 p.m.