Triple
T18016211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SVHN |
E431003
|
entity |
| Predicate | resolutionTypical |
P33105
|
FINISHED |
| Object | 32x32 pixels |
—
|
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: 32x32 pixels | Statement: [SVHN, resolutionTypical, 32x32 pixels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolutionTypical Context triple: [SVHN, resolutionTypical, 32x32 pixels]
-
A.
resolutionStandard
Indicates that something conforms to, or is evaluated against, a specified level or standard of resolution (e.g., detail, clarity, or granularity).
-
B.
typicalResolution
chosen
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
-
C.
resolutionCommon
Indicates that multiple entities share the same resolution or level of detail in a given context.
-
D.
resolutionType
Indicates the specific manner or category by which an issue, event, or conflict is resolved or brought to a conclusion.
-
E.
resolution
Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b523f588819097389e067dda7f23 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.