Triple
T27560844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.261 |
E695764
|
entity |
| Predicate | scanFormat |
P162703
|
FINISHED |
| Object | interlaced video support via progressive source coding tools |
—
|
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: interlaced video support via progressive source coding tools | Statement: [H.261, scanFormat, interlaced video support via progressive source coding tools]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scanFormat Context triple: [H.261, scanFormat, interlaced video support via progressive source coding tools]
-
A.
scanType
Indicates the specific kind or category of scanning operation performed or required in a given context.
-
B.
scanDirection
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
-
C.
scans
Indicates performing a systematic examination or inspection of something, often using a device or method to detect, read, or analyze its contents or structure.
-
D.
sensorFormat
Indicates the data encoding or representation standard used by a sensor to output its measurements.
-
E.
detectorFormat
Indicates the specific data or signal representation used by a detector to encode or output its measurements.
- F. None of above. chosen
Provenance (4 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_69f62fb974e08190a01b9c243e9e8193 |
completed | May 2, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 1:39 p.m.