Triple
T17799235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.723.1 |
E444376
|
entity |
| Predicate | inputSignalType |
P11909
|
FINISHED |
| Object | 8 kHz sampled speech |
—
|
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: 8 kHz sampled speech | Statement: [G.723.1, inputSignalType, 8 kHz sampled speech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputSignalType Context triple: [G.723.1, inputSignalType, 8 kHz sampled speech]
-
A.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
inputType
chosen
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
C.
transportsSignalType
Indicates that one entity carries or conveys a particular type of signal from one point to another.
-
D.
signalProperty
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
-
E.
inputSpecifier
Indicates a relationship where something defines, constrains, or specifies the form, type, or details of an input used in a process or system.
- 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_69e487fe19dc8190b7e9dc96f39e0861 |
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:13 a.m.