Triple
T27866944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CancellationToken |
E704380
|
entity |
| Predicate | supportsCallbackRegistration |
P29001
|
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: [CancellationToken, supportsCallbackRegistration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCallbackRegistration Context triple: [CancellationToken, supportsCallbackRegistration, true]
-
A.
supportsRegistration
chosen
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
B.
supportsUnregisteredUse
Indicates that an entity allows or enables the use of something without requiring prior registration or formal enrollment.
-
C.
supportsRegisterWindows
Indicates that one entity provides functionality to handle or work with register-based windows for another entity.
-
D.
supportsImplementationOf
Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
-
E.
supportedEvent
Indicates that an entity is capable of recognizing, handling, or being associated with a particular type of event.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: April 27, 2026, 6:21 p.m.