Triple
T26379065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OnePlus Warp Charge |
E660973
|
entity |
| Predicate | compatibleDevice |
P126386
|
FINISHED |
| Object | OnePlus 6T McLaren Edition |
—
|
NE NERFINISHED |
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: OnePlus 6T McLaren Edition | Statement: [OnePlus Warp Charge, compatibleDevice, OnePlus 6T McLaren Edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleDevice Context triple: [OnePlus Warp Charge, compatibleDevice, OnePlus 6T McLaren Edition]
-
A.
compatibleSign
Indicates that two entities are considered astrologically harmonious or well-matched based on their zodiac signs.
-
B.
supportedEquipment
chosen
Indicates that one entity provides compatibility with, or operational support for, a specified piece of equipment.
-
C.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
-
D.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
E.
includesDevices
Indicates that one entity contains, encompasses, or has as part of it one or more devices.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 26, 2026, 11:03 p.m.