Triple
T30001605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ProMotion |
E762183
|
entity |
| Predicate | supportsRefreshRate |
P17633
|
FINISHED |
| Object | 60 Hz |
—
|
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: 60 Hz | Statement: [ProMotion, supportsRefreshRate, 60 Hz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRefreshRate Context triple: [ProMotion, supportsRefreshRate, 60 Hz]
-
A.
supportsVariableRefreshRate
Indicates that one entity provides compatibility with or functionality for dynamically adjusting refresh rates in coordination with another entity.
-
B.
displayRefreshRate
chosen
Indicates the frequency at which a display updates its visual content, typically measured in hertz (Hz).
-
C.
supportsFrameRates
Indicates that one entity is capable of operating with, handling, or being compatible with the specified frame rates of another entity.
-
D.
supportsDisplayResolution
Indicates that one entity is capable of operating with, rendering, or otherwise accommodating the specified display resolution of another entity.
-
E.
supportsDRAMRefresh
Indicates that one entity provides the capability or functionality needed to perform DRAM refresh operations for another entity.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 6:41 p.m.