Triple
T13478229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android 12 |
E318303
|
entity |
| Predicate | firstDeveloperPreviewReleaseDate |
P99975
|
FINISHED |
| Object | 2021-02-18 |
—
|
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: 2021-02-18 | Statement: [Android 12, firstDeveloperPreviewReleaseDate, 2021-02-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDeveloperPreviewReleaseDate Context triple: [Android 12, firstDeveloperPreviewReleaseDate, 2021-02-18]
-
A.
earlyAccessReleaseDate
chosen
Indicates the date on which something is first made available to a limited or pre-release audience before its full public release.
-
B.
firstShortReleaseDate
Indicates the earliest (first) date on which a short version or short-format release of something became publicly available.
-
C.
initialReleaseDeveloper
Indicates that the subject entity is the developer responsible for the initial release of the object entity.
-
D.
firstReleaseVersion
Indicates the specific version identifier associated with the initial public release of something.
-
E.
preliminaryVersionDate
Indicates the date on which an initial or draft version of something was created, issued, or became available.
- 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.