Triple
T27735496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ManualResetEvent |
E697517
|
entity |
| Predicate | requiresManualReset |
P163151
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ManualResetEvent, requiresManualReset, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresManualReset Context triple: [ManualResetEvent, requiresManualReset, true]
-
A.
isManualReset
chosen
Indicates whether the reset or reinitialization of the related object or condition must be performed manually rather than occurring automatically.
-
B.
isAutoReset
Indicates that the related mechanism or state automatically returns to its default or initial condition after being triggered or used.
-
C.
requiresInfrastructureManagement
Indicates that one entity depends on another to provide or perform infrastructure management in order for it to function or be fulfilled.
-
D.
requiresLock
Indicates that performing the associated action or accessing the related resource is contingent on acquiring a lock to ensure exclusive or synchronized use.
-
E.
hasManual
Indicates that an entity is associated with a manual that provides instructions or documentation for it.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 27, 2026, 3:12 p.m.