Triple
T31083833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UPC-E |
E792173
|
entity |
| Predicate | printingSpaceRequirement |
P47152
|
FINISHED |
| Object | smaller than UPC-A |
—
|
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: smaller than UPC-A | Statement: [UPC-E, printingSpaceRequirement, smaller than UPC-A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: printingSpaceRequirement Context triple: [UPC-E, printingSpaceRequirement, smaller than UPC-A]
-
A.
printWidth
Indicates the width setting or constraint used when formatting or printing content, such as text or code.
-
B.
spaceRequirements
chosen
Indicates the amount and type of physical or storage space needed for something to be properly placed, installed, or operated.
-
C.
shapeRequirement
Indicates that one entity imposes or specifies a required shape or geometric form that another entity must conform to.
-
D.
projectionRequirement
Indicates a requirement that one entity be projected, mapped, or represented onto another according to specified criteria or constraints.
-
E.
isTypicallyPrinted
Indicates that something is commonly or usually produced in printed form rather than in another medium.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:02 p.m.