Triple
T27735485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ManualResetEvent |
E697517
|
entity |
| Predicate | isSignaledStatePersistent |
P163152
|
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, isSignaledStatePersistent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSignaledStatePersistent Context triple: [ManualResetEvent, isSignaledStatePersistent, true]
-
A.
allowsPersistentStateInProcess
Indicates that an entity permits maintaining persistent state within an ongoing process or execution context.
-
B.
canBeSignaledBy
Indicates that one entity is capable of being triggered, notified, or activated by another entity through some form of signaling.
-
C.
isStateFlagOf
Indicates that one entity is the official state flag representing the specified state or region.
-
D.
firstSignaledBy
Indicates that a particular event, condition, or state was initially brought to attention or detected by a specified entity.
-
E.
isStateRecognized
Indicates that an entity (such as a government, organization, or status) is officially acknowledged and accepted by a state or governing authority.
- 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.