Triple
T5922515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web APIs |
E131730
|
entity |
| Predicate | example |
P1259
|
FINISHED |
| Object | Fetch API |
E131730
|
NE 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: Fetch API | Statement: [Web APIs, example, Fetch API]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fetch API Context triple: [Web APIs, example, Fetch API]
-
A.
Axios
Axios is a digital media company known for its concise, bullet-point-driven coverage of politics, business, technology, and media.
-
B.
REST API
A REST API is a web service interface that allows clients to interact with resources over HTTP using standard methods like GET, POST, PUT, and DELETE in a stateless, structured way.
-
C.
Web APIs
chosen
Web APIs are browser-provided interfaces that enable JavaScript to interact with web platform features such as the DOM, networking, storage, and multimedia beyond the core ECMAScript language.
-
D.
JSON API
JSON API is a standardized specification for building JSON-based RESTful APIs that defines how clients should request and modify resources in a consistent, structured format.
-
E.
Action API
Action API is a web-based interface provided by MediaWiki that allows developers to programmatically read, modify, and manage wiki content and configuration.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03804d9808190829a418adb7864aa |
completed | March 22, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0c041d4f08190863141b037b1c05f |
completed | March 23, 2026, 4:23 a.m. |
Created at: March 22, 2026, 4 p.m.