Triple
T10328808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TransformStreamDefaultController |
E242826
|
entity |
| Predicate | enqueueEffect |
P53074
|
FINISHED |
| Object | adds a chunk to the readable side queue |
—
|
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: adds a chunk to the readable side queue | Statement: [TransformStreamDefaultController, enqueueEffect, adds a chunk to the readable side queue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enqueueEffect Context triple: [TransformStreamDefaultController, enqueueEffect, adds a chunk to the readable side queue]
-
A.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
B.
sideEffect
Indicates that one entity is an unintended or secondary effect resulting from the use or occurrence of another entity.
-
C.
tookEffect
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
-
D.
registrationEffect
Indicates the outcome or consequence that results from an entity being registered or from the act of registration taking place.
-
E.
effectOnSchedule
Indicates how an event, action, or condition changes, disrupts, or influences a planned schedule or timeline.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.