Triple
T10521789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WritableStreamDefaultController |
E248190
|
entity |
| Predicate | methodPurpose(write) |
P26267
|
FINISHED |
| Object | enqueue a chunk into the writable stream |
—
|
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: enqueue a chunk into the writable stream | Statement: [WritableStreamDefaultController, methodPurpose(write), enqueue a chunk into the writable stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodPurpose(write) Context triple: [WritableStreamDefaultController, methodPurpose(write), enqueue a chunk into the writable stream]
-
A.
writesTo
chosen
Indicates that one entity produces and records information, data, or content into another entity as a destination or storage target.
-
B.
wrote
Indicates that an entity is the author or creator of a written work involving another entity.
-
C.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
-
D.
writable
Indicates that one entity has permission or capability to modify or write data to another entity.
-
E.
usedToWrite
Indicates that one entity served as a tool, medium, or instrument that another entity employed to perform the act of writing.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509dec25881909bc748640f26a416 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:29 p.m.