Triple
T29389639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | android.print.PrintAttributes.Resolution |
E745340
|
entity |
| Predicate | returnType:getHorizontalDpi() |
P41264
|
FINISHED |
| Object | int |
—
|
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: int | Statement: [android.print.PrintAttributes.Resolution, returnType:getHorizontalDpi(), int]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnType:getHorizontalDpi() Context triple: [android.print.PrintAttributes.Resolution, returnType:getHorizontalDpi(), int]
-
A.
hasPixelPitch
Indicates the distance between adjacent pixels in a display or image sensor, typically measured from center to center.
-
B.
pixelDensity
chosen
Indicates the number of pixels per unit of length or area used to represent or display a visual element.
-
C.
graphicsDimension
Indicates a relationship where an entity has or is associated with a specific graphical size or dimensional properties.
-
D.
externalDisplayResolution
Indicates the resolution at which content is output or rendered on an external display device.
-
E.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
- 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_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 2:41 p.m.