Triple
T27560851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.261 |
E695764
|
entity |
| Predicate | usesPictureTypes |
P117883
|
FINISHED |
| Object | intra-coded pictures |
—
|
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: intra-coded pictures | Statement: [H.261, usesPictureTypes, intra-coded pictures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPictureTypes Context triple: [H.261, usesPictureTypes, intra-coded pictures]
-
A.
typicalPictureFormat
Indicates the standard or most commonly used picture format associated with an entity (such as a device, medium, or context).
-
B.
usesImageModel
Indicates that one entity employs or relies on an image-based model (such as a computer vision or image generation model) in relation to another entity or task.
-
C.
usesImagery
Indicates that one entity employs descriptive or figurative language to create sensory or vivid mental images in relation to another entity or concept.
-
D.
usesCameraType
Indicates that one entity employs or operates a specific type or category of camera.
-
E.
principalImageType
chosen
Indicates the primary or most representative type of image associated with an 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 1:39 p.m.