Triple
T27582109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SVGA |
E699609
|
entity |
| Predicate | supportsHigherResolutionThan |
P74451
|
FINISHED |
| Object | VGA |
—
|
NE NERFINISHED |
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: VGA | Statement: [SVGA, supportsHigherResolutionThan, VGA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHigherResolutionThan Context triple: [SVGA, supportsHigherResolutionThan, VGA]
-
A.
hasHigherResolutionThan
Indicates that one entity has a greater level of detail or clarity in its representation or measurement than another entity.
-
B.
supportsDisplayResolution
chosen
Indicates that one entity is capable of operating with, rendering, or otherwise accommodating the specified display resolution of another entity.
-
C.
hasHigherQualityThan
Indicates that one entity possesses a superior level of quality compared to another entity.
-
D.
resolutionSupport
Indicates that one entity provides assistance, resources, or mechanisms that help resolve a problem, conflict, or issue involving another entity.
-
E.
hasCameraResolution
Indicates that an entity is associated with a specific camera resolution value or specification.
- 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_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: April 27, 2026, 2:03 p.m.