Triple
T29482809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fetch API |
E747835
|
entity |
| Predicate | returnTypeOfFetch |
P85669
|
FINISHED |
| Object | 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: Promise | Statement: [Fetch API, returnTypeOfFetch, Promise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnTypeOfFetch Context triple: [Fetch API, returnTypeOfFetch, Promise]
-
A.
typeOfResponse
Indicates the specific kind or category of reply or reaction that is given in response to a preceding action, event, or input.
-
B.
bodyReturnType
chosen
Indicates the data type of the value that a method or function returns in its response body.
-
C.
resultType
Indicates the type or category of outcome that is produced by a given process, action, or operation.
-
D.
returnsFromGetItem
Indicates that an entity is the value returned as a result of performing a "get item" retrieval operation on another entity.
-
E.
returnTypeForModuleOverload
Indicates the return type associated with a specific overloaded function or method within a module.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 4:05 p.m.