Triple
T29389435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | android.print.PrintAttributes |
E745335
|
entity |
| Predicate | supportsMonochromePrinting |
P21150
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [android.print.PrintAttributes, supportsMonochromePrinting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMonochromePrinting Context triple: [android.print.PrintAttributes, supportsMonochromePrinting, true]
-
A.
supportsMonochromeMonitor
Indicates that one entity is capable of operating with, driving, or is compatible with a monochrome (single-color) monitor.
-
B.
printingColor
Indicates that one entity uses or displays a specific color in the context of printing or printed output.
-
C.
hasPrintFeature
chosen
Indicates that an entity possesses a specific printing-related characteristic or capability.
-
D.
printingSupport
Indicates that one entity provides or is compatible with printing capabilities or services for another entity.
-
E.
printedInColor
Indicates that something was produced or reproduced using multiple ink colors rather than only black-and-white.
- 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_6a03352bb9688190b965d188769fcacd |
completed | May 12, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_6a033329ae5c81909532843fe716ec77 |
completed | May 12, 2026, 2:03 p.m. |
Created at: April 28, 2026, 2:41 p.m.