Triple
T38543698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beacon API |
E924907
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object |
W3C Beacon specification
The W3C Beacon specification is a web standard that defines a simple, asynchronous API for reliably sending small amounts of data from the browser to a server, typically for analytics and diagnostics, without blocking page unload or affecting performance.
|
E2274422
|
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: W3C Beacon specification | Statement: [Beacon API, definedIn, W3C Beacon specification]
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: W3C Beacon specification Triple: [Beacon API, definedIn, W3C Beacon specification]
Generated description
The W3C Beacon specification is a web standard that defines a simple, asynchronous API for reliably sending small amounts of data from the browser to a server, typically for analytics and diagnostics, without blocking page unload or affecting performance.
Provenance (5 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd2ec6ab88190b83ae99d390453f3 |
completed | May 7, 2026, 5:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41e035391c8190aeb0f9ae822b2269 |
completed | June 29, 2026, 3:02 a.m. |
| NEDg | Description generation | batch_6a41e19145f48190a1be014573a35c24 |
completed | June 29, 2026, 3:08 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a41e205f6e08190be4ce8b46c8aec9c |
completed | June 29, 2026, 3:09 a.m. |
Created at: May 3, 2026, 4:32 p.m.