Triple
T30001604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ProMotion |
E762183
|
entity |
| Predicate | typicalMaxRefreshRate |
P68881
|
FINISHED |
| Object | 120 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: 120 Hz | Statement: [ProMotion, typicalMaxRefreshRate, 120 Hz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMaxRefreshRate Context triple: [ProMotion, typicalMaxRefreshRate, 120 Hz]
-
A.
supportsVariableRefreshRate
Indicates that one entity provides compatibility with or functionality for dynamically adjusting refresh rates in coordination with another entity.
-
B.
displayRefreshRate
Indicates the frequency at which a display updates its visual content, typically measured in hertz (Hz).
-
C.
propertyType_maxFramerate
chosen
Indicates the maximum frame rate value that the property can support or is configured to allow.
-
D.
commonFrameRate
Indicates that two or more media items share the same frame rate.
-
E.
typicalResolution
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
- 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_6a0332a08b48819094aaed6e04a36886 |
completed | May 12, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_6a0331998a688190b5d919697d4231ac |
completed | May 12, 2026, 1:56 p.m. |
Created at: April 29, 2026, 6:41 p.m.