Triple
T10540941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacBook Pro (14-inch, 2023) |
E248692
|
entity |
| Predicate | maxRefreshRate |
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: [MacBook Pro (14-inch, 2023), maxRefreshRate, 120 Hz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxRefreshRate Context triple: [MacBook Pro (14-inch, 2023), maxRefreshRate, 120 Hz]
-
A.
supportsVariableRefreshRate
Indicates that one entity provides compatibility with or functionality for dynamically adjusting refresh rates in coordination with another entity.
-
B.
maxCurrent
Indicates the maximum electric current that is allowed to flow through or be drawn by an entity under specified conditions.
-
C.
maximumResolution
Indicates the highest level of detail or fineness at which something (such as an image, display, or measurement) can be represented or processed.
-
D.
displayRefreshRate
Indicates the frequency at which a display updates its visual content, typically measured in hertz (Hz).
-
E.
propertyType_maxFramerate
chosen
Indicates the maximum frame rate value that the property can support or is configured to allow.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a5918648190b16c2d1bc1bf015f |
completed | April 7, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:32 p.m.