Triple
T2663185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 13-inch MacBook Pro (M2, 2022) |
E54771
|
entity |
| Predicate | maximumBrightness |
P41265
|
FINISHED |
| Object | 500 nits |
—
|
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: 500 nits | Statement: [13-inch MacBook Pro (M2, 2022), maximumBrightness, 500 nits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumBrightness Context triple: [13-inch MacBook Pro (M2, 2022), maximumBrightness, 500 nits]
-
A.
maximumIntensity
Indicates the greatest level or strength that a quantity, effect, or signal can reach within a given context.
-
B.
maximumResolution
Indicates the highest level of detail or fineness at which something (such as an image, display, or measurement) can be represented or processed.
-
C.
apparentBrightness
Indicates how bright one object appears from the perspective or location of another, regardless of its actual intrinsic luminosity.
-
D.
maximumNumber
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
E.
maxVoltage
Indicates the maximum electrical potential (voltage) that an entity can safely or normally handle, provide, or operate at.
- F. None of above. chosen
Provenance (4 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd96b9f1c8190a8a9460ca88a9aaf |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8dd05c48190b4f90031642c4091 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:53 p.m.