Triple
T17806054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.726 |
E444560
|
entity |
| Predicate | typicalSampleSize |
P55466
|
FINISHED |
| Object | 16-bit linear PCM equivalent |
—
|
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: 16-bit linear PCM equivalent | Statement: [G.726, typicalSampleSize, 16-bit linear PCM equivalent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSampleSize Context triple: [G.726, typicalSampleSize, 16-bit linear PCM equivalent]
-
A.
typicalSampleSizeRuleOfThumb
Indicates a heuristic guideline that specifies a commonly recommended sample size to use in typical situations or standard study designs.
-
B.
sampleSize
chosen
Indicates the number of units, observations, or instances included in a particular study, experiment, or dataset.
-
C.
typicalClassSize
Indicates the usual or average number of students (or participants) that are present in a single class or course section.
-
D.
typicalGroupSize
Indicates the usual or characteristic number of individuals that typically form a group in this context.
-
E.
hasTypicalMemberSize
Indicates the usual or characteristic size associated with members of a given class or group.
- 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_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. |
Created at: April 10, 2026, 10:14 a.m.