Triple
T36077437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android 12 |
E1043533
|
entity |
| Predicate | firstStableReleaseDevice |
P114218
|
FINISHED |
| Object | Google Pixel smartphones |
E72242
|
NE 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: Google Pixel smartphones | Statement: [Android 12, firstStableReleaseDevice, Google Pixel smartphones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstStableReleaseDevice Context triple: [Android 12, firstStableReleaseDevice, Google Pixel smartphones]
-
A.
firstPublicReleaseDevice
chosen
Indicates that the subject is the device on which something (e.g., a product, feature, or software) was first publicly released.
-
B.
firstStableBuildReleasedOn
Indicates the date on which the first stable (non-beta) build of something was officially released.
-
C.
firstDevices
Indicates that the related entities are devices that occur or are used first in a sequence, order, or process relative to other devices.
-
D.
firstReleasePlatform
Indicates the platform on which something (such as a product, work, or media) was first released.
-
E.
platformFirstReleased
Indicates the date or time when a platform was initially released or made publicly available.
- F. None of above.
Provenance (4 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38d53e8dfc819095ae213a57f4b030 |
completed | June 22, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.