Triple
T28828470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pixel Feature Drop March 2022 |
E727976
|
entity |
| Predicate | hasVersionBase |
P171800
|
FINISHED |
| Object | Android 12 |
—
|
NE NERFINISHED |
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 12 | Statement: [Pixel Feature Drop March 2022, hasVersionBase, Android 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVersionBase Context triple: [Pixel Feature Drop March 2022, hasVersionBase, Android 12]
-
A.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
B.
hasVersionType
Indicates that one entity is associated with a specific kind or category of version of another entity.
-
C.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
-
D.
hasFirstVersion
Indicates that one entity is the earliest or original version in a sequence of versions related to another entity.
-
E.
hasStandardVersion
Indicates that one entity serves as the official or canonical version of another entity.
- F. None of above. chosen
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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 28, 2026, 6:36 a.m.