Triple
T37163859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorbis |
E920743
|
entity |
| Predicate | referenceDecoder |
P130226
|
FINISHED |
| Object | libvorbis |
—
|
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: libvorbis | Statement: [Vorbis, referenceDecoder, libvorbis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceDecoder Context triple: [Vorbis, referenceDecoder, libvorbis]
-
A.
decodingAbstraction
Indicates the process or relationship by which a concrete encoded form is interpreted into a more general, conceptual, or higher-level representation.
-
B.
openSourceDecoder
Indicates that the decoder component is released as open-source software, allowing public access, use, modification, and distribution of its source code.
-
C.
decoderType
chosen
Indicates the specific kind or category of decoder associated with or used by an entity.
-
D.
decodingMethod
Indicates the technique or process used to convert encoded or encrypted data back into its original, interpretable form.
-
E.
decodingStage
Indicates the stage or phase in a decoding process at which a particular action, transformation, or state occurs.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: May 3, 2026, 4:15 p.m.