Triple
T17218064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saorsat |
E417902
|
entity |
| Predicate | compressionFormat |
P27672
|
FINISHED |
| Object | MPEG-4 AVC |
—
|
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: MPEG-4 AVC | Statement: [Saorsat, compressionFormat, MPEG-4 AVC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compressionFormat Context triple: [Saorsat, compressionFormat, MPEG-4 AVC]
-
A.
compressionType
chosen
Indicates the method or format used to compress data or content in the relationship.
-
B.
compressionLoss
Indicates that some amount of information, quality, or fidelity is lost as a result of a compression process.
-
C.
compressionCharacteristic
Indicates how an entity behaves or performs when subjected to compressive forces or pressure.
-
D.
compressionGoal
Indicates the target level or outcome of data size reduction that a compression process aims to achieve.
-
E.
compressionRatio
Indicates the proportional reduction in size or volume achieved when something is compressed compared to its original size.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddb2b148190b3b50572cc285e3d |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.