Triple
T8611268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Android system print framework |
E203918
|
entity |
| Predicate | availableSinceApiLevel |
P11235
|
FINISHED |
| Object | 19 |
—
|
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: 19 | Statement: [Android system print framework, availableSinceApiLevel, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableSinceApiLevel Context triple: [Android system print framework, availableSinceApiLevel, 19]
-
A.
officialVersionSince
Indicates the point in time from which a particular version of something is recognized or treated as the official version.
-
B.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
C.
introducedWithVersion
chosen
Indicates that something first became available or was added starting from a specific version.
-
D.
laterVersionsCapability
Indicates that one entity has the capability to support, handle, or be compatible with later versions of another entity.
-
E.
hasSupported
Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fc31e08190aab5ab8f92f3315c |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.