Triple
T9002169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VC-1 |
E215061
|
entity |
| Predicate | compressionGoal |
P85661
|
FINISHED |
| Object | high compression efficiency for HD content |
—
|
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: high compression efficiency for HD content | Statement: [VC-1, compressionGoal, high compression efficiency for HD content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compressionGoal Context triple: [VC-1, compressionGoal, high compression efficiency for HD content]
-
A.
compressionType
Indicates the method or format used to compress data or content in the relationship.
-
B.
compressionRatio
Indicates the proportional reduction in size or volume achieved when something is compressed compared to its original size.
-
C.
compressionScope
Indicates the extent or range within which compression is applied to data or content.
-
D.
compressionDomain
Indicates a relationship where one entity serves as the domain or context within which another entity’s compression or compression-related process is defined or applied.
-
E.
compressionAxis
Indicates the primary direction along which a force or process compresses an object or material.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6956a6e08190bd3853a7c1c130eb |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:05 p.m.