Triple
T13478271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android 12 |
E318303
|
entity |
| Predicate | targetDevices |
P86660
|
FINISHED |
| Object | Android smartphones |
—
|
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: Android smartphones | Statement: [Android 12, targetDevices, Android smartphones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetDevices Context triple: [Android 12, targetDevices, Android smartphones]
-
A.
targetedDevice
chosen
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
B.
includesDevices
Indicates that one entity contains, encompasses, or has as part of it one or more devices.
-
C.
targetVendorDevice
Indicates that a device is specifically associated with or designated as the target device for a particular vendor.
-
D.
relatedDevice
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
-
E.
marketsDevicesUnderBrand
Indicates that an entity promotes and sells devices using a particular brand name or under a specific brand identity.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf266c508190930d30776c09ce35 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.