Triple

T4786487
Position Surface form Disambiguated ID Type / Status
Subject Double-Barreled Cannon E106490 entity
Predicate firingRequirement P51083 FINISHED
Object simultaneous discharge of both barrels 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: simultaneous discharge of both barrels | Statement: [Double-Barreled Cannon, firingRequirement, simultaneous discharge of both barrels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: firingRequirement
Context triple: [Double-Barreled Cannon, firingRequirement, simultaneous discharge of both barrels]
  • A. maintenanceRequirement
    Indicates that an entity is obligated to perform, schedule, or adhere to specific maintenance activities or conditions for another entity or system.
  • B. requires
    Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
  • C. proceduralRequirement chosen
    Indicates that one entity specifies or imposes a required procedure or process that must be followed by another entity.
  • D. frequencyRequirement
    Indicates a constraint specifying how often an action, event, or condition must occur within a given context or time frame.
  • E. establishedRequirement
    Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
  • 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_69bd43f4a9588190bf73e20bc27c03cc completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd65d8f9d881909c24340b8dc6a104 completed March 20, 2026, 3:20 p.m.
PD Predicate disambiguation batch_69bd622e1b408190806c15c61519fc74 completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:22 p.m.