Triple
T27736149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RegisteredWaitHandle |
E697532
|
entity |
| Predicate | UnregisterParameterType |
P32992
|
FINISHED |
| Object | WaitHandle |
—
|
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: WaitHandle | Statement: [RegisteredWaitHandle, UnregisterParameterType, WaitHandle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UnregisterParameterType Context triple: [RegisteredWaitHandle, UnregisterParameterType, WaitHandle]
-
A.
dataTypeCleared
Indicates that a previously assigned or stored data type has been removed or reset to an undefined or default state.
-
B.
clearsProductType
chosen
Indicates that one entity removes or resets the specified product type association from another entity.
-
C.
UNDesignation
Indicates that an entity has been formally assigned a specific status, role, or classification by the United Nations.
-
D.
delegateType
Indicates that one entity serves as a delegate of a specified type or role in relation to another entity.
-
E.
usesRegisterType
Indicates that one entity employs or relies on a specific type or category of register in its operation or representation.
- 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_69f636a088b8819081e34d416b28cdac |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:12 p.m.