Triple
T22041274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Performance API |
E544641
|
entity |
| Predicate | includesSpecification |
P19701
|
FINISHED |
| Object | Navigation Timing Level 2 |
—
|
NE NERFINISHED |
How this triple was built (3 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: Navigation Timing Level 2 | Statement: [Web Performance API, includesSpecification, Navigation Timing Level 2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Navigation Timing Level 2 Context triple: [Web Performance API, includesSpecification, Navigation Timing Level 2]
-
A.
Resource Timing Level 2
Resource Timing Level 2 is a W3C specification that defines an API for collecting detailed timing metrics about the loading of web resources to help analyze and optimize web performance.
-
B.
Web performance API
The Web performance API is a set of browser interfaces that enable precise measurement, analysis, and optimization of web page and application performance.
-
C.
Resource Timing API
The Resource Timing API is a web performance interface that lets developers measure and analyze detailed timing data for the loading of page resources such as images, scripts, and stylesheets.
-
D.
PerformanceResourceTiming
PerformanceResourceTiming is a Web Performance API interface that provides detailed timing metrics about the loading of specific resource requests, such as scripts, images, and stylesheets.
-
E.
Event Timing API
The Event Timing API is a web performance interface that lets developers measure the latency and timing of user interactions, such as clicks and key presses, to better understand and optimize user experience.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Navigation Timing Level 2 Target entity description: Navigation Timing Level 2 is a W3C specification that defines high-resolution browser APIs for measuring and analyzing the performance of web page navigation and loading.
-
A.
Resource Timing Level 2
Resource Timing Level 2 is a W3C specification that defines an API for collecting detailed timing metrics about the loading of web resources to help analyze and optimize web performance.
-
B.
Web performance API
The Web performance API is a set of browser interfaces that enable precise measurement, analysis, and optimization of web page and application performance.
-
C.
Resource Timing API
The Resource Timing API is a web performance interface that lets developers measure and analyze detailed timing data for the loading of page resources such as images, scripts, and stylesheets.
-
D.
PerformanceResourceTiming
PerformanceResourceTiming is a Web Performance API interface that provides detailed timing metrics about the loading of specific resource requests, such as scripts, images, and stylesheets.
-
E.
Event Timing API
The Event Timing API is a web performance interface that lets developers measure the latency and timing of user interactions, such as clicks and key presses, to better understand and optimize user experience.
- F. None of above. chosen
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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12828fc788190a22c0e9c2372656b |
completed | April 28, 2026, 9:35 p.m. |
Created at: April 16, 2026, 8:25 p.m.