Triple
T32062389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPEG-4 CELP |
E818777
|
entity |
| Predicate | signalModel |
P173504
|
FINISHED |
| Object | source-filter model of 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: source-filter model of speech | Statement: [MPEG-4 CELP, signalModel, source-filter model of speech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalModel Context triple: [MPEG-4 CELP, signalModel, source-filter model of speech]
-
A.
signalType
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
signalProperty
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
-
C.
signalReception
Indicates the reception or detection of a transmitted signal by a receiving entity.
-
D.
signalingMode
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
-
E.
signalContent
Indicates that one entity is the informational content or message carried, conveyed, or represented by a signal produced or transmitted by another entity.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:22 a.m.