Triple
T15089961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrome OS devices |
E360387
|
entity |
| Predicate | firstCommercialDevicesReleased |
P40835
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Chrome OS devices, firstCommercialDevicesReleased, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCommercialDevicesReleased Context triple: [Chrome OS devices, firstCommercialDevicesReleased, 2011]
-
A.
wasFirstCommercializedBy
Indicates that the subject was initially brought to market or made commercially available by the object.
-
B.
firstPublicReleaseDevice
Indicates that the subject is the device on which something (e.g., a product, feature, or software) was first publicly released.
-
C.
firstCommercialReleaseYear
chosen
Indicates the calendar year in which something (such as a product, work, or service) was first made commercially available to the public.
-
D.
firstDevices
Indicates that the related entities are devices that occur or are used first in a sequence, order, or process relative to other devices.
-
E.
firstCommercialUse
Indicates the earliest point in time at which something was used commercially or put into commercial operation.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00277ea808190be3f002a8316eff1 |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.