Triple

T10119365
Position Surface form Disambiguated ID Type / Status
Subject Blanketeers march E223243 entity
Predicate wasSuppressedBy P92077 FINISHED
Object authorities 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: authorities | Statement: [Blanketeers march, wasSuppressedBy, authorities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasSuppressedBy
Context triple: [Blanketeers march, wasSuppressedBy, authorities]
  • A. wasSupersededBy
    Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
  • B. typeOfSuppression
    Indicates the specific manner or mechanism by which something is suppressed, inhibited, or prevented from occurring or being expressed.
  • C. suppressedOn
    Indicates that one entity is intentionally prevented, hidden, or blocked from being shown, executed, or taking effect in the context of another entity.
  • D. suppressedIn
    Indicates that one entity’s presence, activity, or expression is reduced, inhibited, or prevented by another entity or condition.
  • E. overshadowedBy
    Indicates that one entity’s importance, visibility, or impact is diminished because another entity is more prominent or dominant.
  • 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_69ca8422047c81909d66b717b8b18cf3 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cdd26460a4819093a3b239d97c3e3d completed April 2, 2026, 2:20 a.m.
PD Predicate disambiguation batch_69cd4ba1d360819087698d04a53cc87e completed April 1, 2026, 4:45 p.m.
PDg Predicate description generation batch_69cd4fed19d481909d2c7ff1114664b6 completed April 1, 2026, 5:03 p.m.
Created at: March 30, 2026, 9:04 p.m.