Triple
T22142963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple A6X |
E547211
|
entity |
| Predicate | intendedDevice |
P86660
|
FINISHED |
| Object | tablet computer |
—
|
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: tablet computer | Statement: [Apple A6X, intendedDevice, tablet computer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedDevice Context triple: [Apple A6X, intendedDevice, tablet computer]
-
A.
targetedDevice
chosen
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
B.
usesDevice
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
C.
testedDeviceType
Indicates that one entity is the type or category of device on which another entity has been tested.
-
D.
testedDevice
Indicates that one entity has performed a test on, or experimentally evaluated, another entity as a device.
-
E.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bf78108190b50d937917258693 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.