Triple
T17806062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.726 |
E444560
|
entity |
| Predicate | bitstreamType |
P128991
|
FINISHED |
| Object | sample-by-sample ADPCM |
—
|
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: sample-by-sample ADPCM | Statement: [G.726, bitstreamType, sample-by-sample ADPCM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitstreamType Context triple: [G.726, bitstreamType, sample-by-sample ADPCM]
-
A.
bitstream
Indicates a relationship where data is represented or transmitted as a continuous sequence of bits in a defined order.
-
B.
bitstreamVersion
Indicates the specific version identifier assigned to a given bitstream within a digital object or system.
-
C.
binaryType
Indicates that something is classified as a binary type, typically distinguishing between two mutually exclusive categories or values.
-
D.
bitOrder
Indicates the ordering or sequence of bits within a binary representation, such as which bit positions are considered first or most significant.
-
E.
bitWidth
Indicates the number of bits used to represent or encode a given value, type, or data element.
- F. None of above. chosen
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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4880385b48190b8dea0f05dfa1300 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:14 a.m.