Triple
T11941795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kodak printers |
E284194
|
entity |
| Predicate | supportsMediaSize |
P102383
|
FINISHED |
| Object | 4x6 inch photo paper |
—
|
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: 4x6 inch photo paper | Statement: [Kodak printers, supportsMediaSize, 4x6 inch photo paper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMediaSize Context triple: [Kodak printers, supportsMediaSize, 4x6 inch photo paper]
-
A.
supportsMediaManagement
Indicates that one entity provides functionality or assistance for organizing, handling, or controlling media content for another entity.
-
B.
supportedBlockSizes
Indicates the specific block sizes that an entity is capable of handling or operating with.
-
C.
spriteSizeSupport
Indicates that an entity supports handling or displaying sprites at specific sizes or resolutions.
-
D.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
E.
desiredSizeIndicates
Indicates that one entity specifies or reflects the preferred or intended size of another entity.
- F. None of above. chosen
Provenance (4 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90342bb908190a019ac91a2b82f3d |
completed | April 10, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:45 p.m.