Triple
T13557258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android 14 |
E323806
|
entity |
| Predicate | introducedForDevices |
P37905
|
FINISHED |
| Object | Pixel 4a 5G and later (official Google support) |
—
|
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: Pixel 4a 5G and later (official Google support) | Statement: [Android 14, introducedForDevices, Pixel 4a 5G and later (official Google support)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedForDevices Context triple: [Android 14, introducedForDevices, Pixel 4a 5G and later (official Google support)]
-
A.
includesDevices
Indicates that one entity contains, encompasses, or has as part of it one or more devices.
-
B.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
C.
introducedInProduct
Indicates that something (such as a feature, component, or concept) first appeared or was initially made available within a particular product.
-
D.
announcedWithDevice
Indicates that an announcement or communication was made using a specific device as the medium or tool.
-
E.
introducedForModel
chosen
Indicates that one entity was created, proposed, or brought into use specifically for application within a particular model.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.