Triple
T22374605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperAgent |
E553121
|
entity |
| Predicate | competesWith |
P1375
|
FINISHED |
| Object | Fetch API |
—
|
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: Fetch API | Statement: [SuperAgent, competesWith, Fetch API]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fetch API Context triple: [SuperAgent, competesWith, Fetch API]
-
A.
Fetch API
chosen
The Fetch API is a modern JavaScript interface for making asynchronous HTTP requests and handling network resources in web applications.
-
B.
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.
-
C.
Api
Api is a Scythian goddess associated with the earth and fertility in ancient Eurasian steppe religion.
-
D.
EFetch
EFetch is an NCBI E-utilities web service that retrieves full records from NCBI databases in various formats based on supplied identifiers.
-
E.
Axios
Axios is a digital media company known for its concise, bullet-point-driven coverage of politics, business, technology, and media.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15806b534819083716c2b090ede42 |
completed | April 29, 2026, 12:59 a.m. |
Created at: April 16, 2026, 8:45 p.m.