Triple
T27560840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.261 |
E695764
|
entity |
| Predicate | usesEntropyCoding |
P163501
|
FINISHED |
| Object | variable-length coding |
—
|
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: variable-length coding | Statement: [H.261, usesEntropyCoding, variable-length coding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEntropyCoding Context triple: [H.261, usesEntropyCoding, variable-length coding]
-
A.
hasEntropy
Indicates that an entity possesses or is characterized by a certain amount or state of entropy, typically reflecting its degree of disorder or uncertainty.
-
B.
usesEncoder
Indicates that one entity employs or relies on an encoder component or mechanism to perform its function or process data.
-
C.
usesScrambling
Indicates that one entity applies a scrambling process or technique to another entity or to information associated with it.
-
D.
usesCodec
Indicates that one entity employs or relies on a specific codec to encode, decode, or process data.
-
E.
encodes
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
- 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_69f6397b64f881909d811225e57aac5e |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 1:39 p.m.