Triple
T22041277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Performance API |
E544641
|
entity |
| Predicate | usesTimeResolution |
P93350
|
FINISHED |
| Object | high-resolution timestamps |
—
|
LITERAL 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: high-resolution timestamps | Statement: [Web Performance API, usesTimeResolution, high-resolution timestamps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTimeResolution Context triple: [Web Performance API, usesTimeResolution, high-resolution timestamps]
-
A.
hasTemporalResolution
chosen
Indicates that one entity specifies the level of temporal detail or granularity at which another entity’s data, observation, or process is measured or represented.
-
B.
timeGranularity
Indicates the level of temporal detail or precision at which an event, measurement, or relationship is defined (e.g., seconds, days, months).
-
C.
timeSensitivity
Indicates how strongly the relationship or action depends on, changes with, or is constrained by time.
-
D.
requiresTiming
Indicates that one entity’s occurrence, execution, or validity depends on being coordinated with a specific time or temporal condition related to another entity.
-
E.
usesTimingRules
Indicates that one entity applies or operates according to specified timing rules or constraints in relation to another entity or process.
- F. None of above.
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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12828fc788190a22c0e9c2372656b |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.