Triple
T17806064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.726 |
E444560
|
entity |
| Predicate | outputSignalType |
P92
|
FINISHED |
| Object | compressed 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: compressed ADPCM | Statement: [G.726, outputSignalType, compressed ADPCM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputSignalType Context triple: [G.726, outputSignalType, compressed ADPCM]
-
A.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
transportsSignalType
Indicates that one entity carries or conveys a particular type of signal from one point to another.
-
C.
outputStageType
Indicates the type or category of the stage at which an output is produced or made available in a process or workflow.
-
D.
hasOutputType
chosen
Indicates that an entity produces, returns, or yields a result of a specified type.
-
E.
signalOfResult
Indicates that one entity functions as a signal, marker, or indicator that a particular result, outcome, or state has occurred or will occur.
- 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.