Triple
T27582111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SVGA |
E699609
|
entity |
| Predicate | typicalMaxResolution |
P38745
|
FINISHED |
| Object | 800×600 |
—
|
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: 800×600 | Statement: [SVGA, typicalMaxResolution, 800×600]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMaxResolution Context triple: [SVGA, typicalMaxResolution, 800×600]
-
A.
typicalResolution
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.
-
B.
typicalInputResolution
Indicates the usual or standard resolution at which input is expected or typically processed.
-
C.
maximumResolution
chosen
Indicates the highest level of detail or fineness at which something (such as an image, display, or measurement) can be represented or processed.
-
D.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
-
E.
mainResolution
Indicates that one resolution is the primary or most important resolution associated with a given context or entity.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
Created at: April 27, 2026, 2:03 p.m.