Triple
T29388512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HFP |
E745313
|
entity |
| Predicate | HFP1.6Introduced |
P16208
|
FINISHED |
| Object | wideband speech support |
—
|
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: wideband speech support | Statement: [HFP, HFP1.6Introduced, wideband speech support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HFP1.6Introduced Context triple: [HFP, HFP1.6Introduced, wideband speech support]
-
A.
radioVersionName
Indicates the specific name or label assigned to a version of a radio-related item or system.
-
B.
wirelessSupportIntroduced
chosen
Indicates that support for wireless functionality was added or became available for the first time.
-
C.
radioVersionType
Indicates the specific type or category of a radio version associated with an item or entity.
-
D.
supportsBluetoothCodec
Indicates that one entity is capable of using or is compatible with a specified Bluetooth audio codec in its operation or communication.
-
E.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d44b7c8190a79e108c68a7077a |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:40 p.m.