Triple
T10371808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WritableStreamDefaultWriter |
E244400
|
entity |
| Predicate | methodReturnType |
P66398
|
FINISHED |
| Object | write() returns a Promise |
—
|
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: write() returns a Promise | Statement: [WritableStreamDefaultWriter, methodReturnType, write() returns a Promise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodReturnType Context triple: [WritableStreamDefaultWriter, methodReturnType, write() returns a Promise]
-
A.
bodyReturnType
Indicates the data type of the value that a method or function returns in its response body.
-
B.
returnTypeForModuleOverload
chosen
Indicates the return type associated with a specific overloaded function or method within a module.
-
C.
hasMethodType
Indicates that an entity is associated with, or characterized by, a specific type or category of method used or applied in its context.
-
D.
hasReturnVariant
Indicates that an entity has an associated alternative form or version specifically used for returning or sending back.
-
E.
resultType
Indicates the type or category of outcome that is produced by a given process, action, or operation.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e97ed09c8190a3627aa7b5eea62f |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:01 p.m.