Triple
T9209529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacBook Pro (14-inch, 2021) |
E221076
|
entity |
| Predicate | refreshTechnology |
P50242
|
FINISHED |
| Object | ProMotion |
—
|
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: ProMotion | Statement: [MacBook Pro (14-inch, 2021), refreshTechnology, ProMotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refreshTechnology Context triple: [MacBook Pro (14-inch, 2021), refreshTechnology, ProMotion]
-
A.
upgradeTechnology
Indicates improving or replacing existing technology with a more advanced, efficient, or capable version.
-
B.
technologyBasis
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
-
C.
technologyPresent
chosen
Indicates that a particular technology exists, is available, or is currently in use in the given context or situation.
-
D.
technologyLevel
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
-
E.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
- 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9b3c8c081909a688ce699928fc0 |
completed | April 1, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:26 p.m.