Triple
T37480162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UHDTV1 |
E931391
|
entity |
| Predicate | hasResolutionWidth |
P3989
|
FINISHED |
| Object | 3840 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: 3840 pixels | Statement: [UHDTV1, hasResolutionWidth, 3840 pixels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResolutionWidth Context triple: [UHDTV1, hasResolutionWidth, 3840 pixels]
-
A.
hasResolution
Indicates that one entity possesses, specifies, or is associated with a particular level or type of resolution (such as detail, clarity, or granularity) in relation to another entity.
-
B.
hasCameraResolution
Indicates that an entity is associated with a specific camera resolution value or specification.
-
C.
hasWidth
chosen
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
D.
supportsDisplayResolution
Indicates that one entity is capable of operating with, rendering, or otherwise accommodating the specified display resolution of another entity.
-
E.
displayResolution
Indicates the relationship specifying the width and height dimensions at which visual content is rendered or shown on a display.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.