Triple
T22932289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EInfo |
E569471
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | EFetch |
—
|
NE NERFINISHED |
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: EFetch | Statement: [EInfo, relatedTo, EFetch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EFetch Context triple: [EInfo, relatedTo, EFetch]
-
A.
EFetch
chosen
EFetch is an NCBI E-utilities web service that retrieves full records from NCBI databases in various formats based on supplied identifiers.
-
B.
EOFetchSpecification
EOFetchSpecification is a configuration object in Apple’s Enterprise Objects Framework that defines how data is fetched from a persistent store, including criteria, sorting, and limits.
-
C.
Fetch Standard
The Fetch Standard is a web platform specification that defines a modern, unified API and processing model for fetching resources (such as HTTP requests and responses) across browsers and other environments.
-
D.
Background Fetch API
The Background Fetch API is a web platform feature that lets sites download large or long-running resources in the background, continuing even if the page or browser is closed.
-
E.
EGQuery
EGQuery is an NCBI E-utilities tool that provides a summary of how many records match a given search term across all NCBI databases.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813260608190bb9e1ca704c7e12f |
completed | April 29, 2026, 3:55 a.m. |
Created at: April 17, 2026, 3:44 p.m.