Triple
T27735494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ManualResetEvent |
E697517
|
entity |
| Predicate | supportsMultipleWaiters |
P128010
|
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, supportsMultipleWaiters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultipleWaiters Context triple: [ManualResetEvent, supportsMultipleWaiters, true]
-
A.
canWaitFor
Indicates that one entity is able or permitted to delay action or progress until another specified entity or event occurs.
-
B.
hasMultipleHoldersSimultaneously
Indicates that a given item, role, or resource is concurrently possessed, controlled, or occupied by more than one holder at the same time.
-
C.
supportsMultipleSubscribers
chosen
Indicates that the subject can simultaneously accommodate or manage more than one subscriber at the same time.
-
D.
hasVirtualWaiter
Indicates that an entity is served or assisted by a digital or virtual waiter system rather than a human waiter.
-
E.
waitsArePerformedBy
Indicates that instances of waiting are carried out or executed by a particular agent or entity.
- 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_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: April 27, 2026, 3:12 p.m.