Triple

T16754235
Position Surface form Disambiguated ID Type / Status
Subject M67 fragmentation grenade E407167 entity
Predicate delayTime P82883 FINISHED
Object approximately 4–5 seconds 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: approximately 4–5 seconds | Statement: [M67 fragmentation grenade, delayTime, approximately 4–5 seconds]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: delayTime
Context triple: [M67 fragmentation grenade, delayTime, approximately 4–5 seconds]
  • A. delayedBy
    Indicates that one event, process, or action occurs later than expected or planned due to the influence or interference of another factor or entity.
  • B. delayedUntil
    Indicates that the occurrence or effect of one event or condition is postponed and does not take place until a specified later event, time, or condition is reached.
  • C. laterDuration
    Indicates that one event or time interval occurs after another and lasts for a specified duration.
  • D. algorithmicDelay
    Indicates a time lag or postponement that arises specifically from the execution or processing steps of an algorithm.
  • E. timingParameter chosen
    Indicates a relationship where one entity specifies or controls a temporal setting, constraint, or configuration parameter that determines the timing behavior of another entity or process.
  • 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_69d8839174188190909f190097207065 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3abe6b68c8190a5e2a11973f01b8e completed April 18, 2026, 4:05 p.m.
PD Predicate disambiguation batch_69e319cbd79c8190a03587a61c18bec0 completed April 18, 2026, 5:42 a.m.
Created at: April 10, 2026, 5:21 a.m.