Triple
T37163861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vorbis |
E920743
|
entity |
| Predicate | metadataFormat |
P44503
|
FINISHED |
| Object | Vorbis comments |
E920743
|
NE 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: Vorbis comments | Statement: [Vorbis, metadataFormat, Vorbis comments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metadataFormat Context triple: [Vorbis, metadataFormat, Vorbis comments]
-
A.
metadata
Indicates that one entity provides descriptive or contextual information about another entity, such as its properties, origin, or structure.
-
B.
metadataType
chosen
Indicates that one entity specifies the kind or category of metadata associated with another entity.
-
C.
preservationFormat
Indicates the format or encoding in which something is maintained specifically for long-term preservation.
-
D.
materialsFormat
Indicates the relationship between materials and the format or medium in which they are presented, stored, or delivered.
-
E.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
- F. None of above.
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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a402bba279c81908800321a32b6f2c5 |
completed | June 27, 2026, 7:59 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.