Triple
T27736295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AsyncLocal<T> |
E697536
|
entity |
| Predicate | hasEventLikeCallback |
P146325
|
FINISHED |
| Object | ValueChanged |
—
|
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: ValueChanged | Statement: [AsyncLocal<T>, hasEventLikeCallback, ValueChanged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEventLikeCallback Context triple: [AsyncLocal<T>, hasEventLikeCallback, ValueChanged]
-
A.
hasEventHandler
chosen
Indicates that one entity is responsible for handling or responding to events triggered by another entity.
-
B.
hasListeningEvent
Indicates that an entity participates in or is associated with an event in which listening or audio consumption occurs.
-
C.
hasEventType
Indicates that an event is associated with, or classified under, a specific type or category of event.
-
D.
isRelayEvent
Indicates that an event functions as an intermediary or forwarding step within a larger process or communication chain.
-
E.
hasPrimaryEvent
Indicates that an entity is associated with or linked to its main or most significant 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f636a161608190b0cdf03863204034 |
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.