Triple
T29389175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PrintManager |
E745330
|
entity |
| Predicate | availableSinceAPILevel |
P127933
|
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: [PrintManager, availableSinceAPILevel, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableSinceAPILevel Context triple: [PrintManager, availableSinceAPILevel, 19]
-
A.
hasAPILevel
Indicates that one entity is associated with, or conforms to, a specific application programming interface (API) version or level.
-
B.
supportsSinceVersion
chosen
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
C.
hasFunctionSince
Indicates that an entity has held or performed a particular function, role, or capability continuously since a specified point in time.
-
D.
officialVersionSince
Indicates the point in time from which a particular version of something is recognized or treated as the official version.
-
E.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
- 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_69f669d578608190962d35116a01420c |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:41 p.m.