Triple

T22041270
Position Surface form Disambiguated ID Type / Status
Subject Web Performance API E544641 entity
Predicate includesSpecification P19701 FINISHED
Object Long Tasks 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: Long Tasks API | Statement: [Web Performance API, includesSpecification, Long Tasks API]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Long Tasks API
Context triple: [Web Performance API, includesSpecification, Long Tasks API]
  • A. Long Tasks API chosen
    The Long Tasks API is a web performance interface that helps developers detect and measure main-thread tasks that block the browser for too long, enabling them to identify and optimize sources of jank and poor responsiveness.
  • B. Cloud Tasks
    Cloud Tasks is a fully managed Google Cloud service for scheduling, dispatching, and managing asynchronous background tasks at scale.
  • C. JobExecution API
    JobExecution API is a Jakarta Batch component that represents and manages the runtime state and metadata of a batch job execution.
  • D. Delayed Job
    Delayed Job is a Ruby background job processing library that runs tasks asynchronously by storing them in a database-backed queue.
  • E. TaskManager
    TaskManager is a core Apache Flink runtime component responsible for executing tasks, managing their resources, and handling data exchange between parallel processing units.
  • 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_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.