Triple
T37163858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorbis |
E920743
|
entity |
| Predicate | referenceEncoder |
P127370
|
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, referenceEncoder, libvorbis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceEncoder Context triple: [Vorbis, referenceEncoder, libvorbis]
-
A.
openSourceReferenceEncoder
chosen
Indicates that one entity serves as an open-source implementation or encoding reference for another entity.
-
B.
usesEncoder
Indicates that one entity employs or relies on an encoder component or mechanism to perform its function or process data.
-
C.
encodes
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
-
D.
relatedCodec
Indicates that one entity is associated with or corresponds to another through a shared or compatible codec used for encoding or decoding data.
-
E.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
- 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_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:15 p.m.