Triple
T28771976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xvid |
E726433
|
entity |
| Predicate | hasEncoder |
P130213
|
FINISHED |
| Object | Xvid encoder |
—
|
NE NERFINISHED |
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: Xvid encoder | Statement: [Xvid, hasEncoder, Xvid encoder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEncoder Context triple: [Xvid, hasEncoder, Xvid encoder]
-
A.
usesEncoder
chosen
Indicates that one entity employs or relies on an encoder component or mechanism to perform its function or process data.
-
B.
hasCompressor
Indicates that one entity is equipped with, contains, or uses a compressor associated with it.
-
C.
isBinaryEncoded
Indicates that information, data, or a value is represented using a binary (base-2) encoding scheme.
-
D.
encodingIs
Indicates that one entity serves as the specific encoding or coded representation of another entity.
-
E.
hasChannelCoding
Indicates that an entity employs a specific channel coding scheme to protect data during transmission over a communication channel.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 6:16 a.m.