Triple
T14441531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android L |
E358092
|
entity |
| Predicate | hasAPILevel |
P114289
|
FINISHED |
| Object | 21 (Android 5.0) |
—
|
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: 21 (Android 5.0) | Statement: [Android L, hasAPILevel, 21 (Android 5.0)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAPILevel Context triple: [Android L, hasAPILevel, 21 (Android 5.0)]
-
A.
hasAndroid
Indicates that an entity possesses, is equipped with, or is associated with an Android device, system, or component.
-
B.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
C.
hasSupported
Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
-
D.
hasUsageLevel
Indicates the degree or intensity with which something is used or utilized.
-
E.
hasAPIs
Indicates that one entity provides or exposes application programming interfaces (APIs) that can be used or accessed by 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de914c1398819090fa2a74d257ba3e |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:18 a.m.