Triple

T27735473
Position Surface form Disambiguated ID Type / Status
Subject ManualResetEvent E697517 entity
Predicate isAutoReset P163150 FINISHED
Object false 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: false | Statement: [ManualResetEvent, isAutoReset, false]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isAutoReset
Context triple: [ManualResetEvent, isAutoReset, false]
  • A. isSelfSynchronizing
    Indicates that a process, system, or component can automatically align its timing or state with others without requiring external coordination or control.
  • B. isContinuous
    Indicates that a function, process, or relationship changes smoothly without abrupt jumps or breaks over its domain.
  • C. isSingleShot
    Indicates that an action or event occurs only once in a single, non-repeating instance.
  • D. isClosed
    Indicates that an entity, process, or structure is in a finished, sealed, or non-open state, preventing further change or access.
  • E. isTypicallyImplementedWithFixedStepSize
    Indicates that the action or process is usually carried out using a constant, unchanging step size rather than a variable one.
  • 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f636a088b8819081e34d416b28cdac completed May 2, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69f63188e7408190af8ce8b93d128c63 completed May 2, 2026, 5:16 p.m.
PDg Predicate description generation batch_69f6352df6148190bc10772cd40bd7b3 completed May 2, 2026, 5:32 p.m.
Created at: April 27, 2026, 3:12 p.m.