Triple
T29389222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PrintDocumentAdapter |
E745331
|
entity |
| Predicate | introducedInApiLevel |
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: [PrintDocumentAdapter, introducedInApiLevel, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInApiLevel Context triple: [PrintDocumentAdapter, introducedInApiLevel, 19]
-
A.
hasAPILevel
Indicates that one entity is associated with, or conforms to, a specific application programming interface (API) version or level.
-
B.
introducedWithVersion
chosen
Indicates that something first became available or was added starting from a specific version.
-
C.
introducedVersionOf
Indicates that one entity is the version in which another entity was first introduced or made available.
-
D.
introducedInSystem
Indicates that an entity was first added, implemented, or made available within a particular system.
-
E.
methodIntroducedWith
Indicates that one method is introduced, defined, or presented together with another method as part of the same conceptual or procedural context.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 28, 2026, 2:41 p.m.