Triple
T32062390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPEG-4 CELP |
E818777
|
entity |
| Predicate | excitationType |
P173173
|
FINISHED |
| Object | codebook-excited signal |
—
|
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: codebook-excited signal | Statement: [MPEG-4 CELP, excitationType, codebook-excited signal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excitationType Context triple: [MPEG-4 CELP, excitationType, codebook-excited signal]
-
A.
excites
Indicates that one entity causes another entity to become excited, stimulated, or activated, typically by increasing its energy or arousal level.
-
B.
stimulusType
Indicates the kind or category of stimulus involved in the relationship or action.
-
C.
exposureType
Indicates the specific manner or context in which one entity is exposed to another entity, condition, or influence.
-
D.
dominantExcitationSource
Indicates that one entity serves as the primary or most influential source of excitation affecting another entity or system.
-
E.
provokesEmotionType
Indicates that one entity causes or elicits a specific type of emotional response in 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_69f6b4f638908190957f64096c07535f |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b267b90c8190807208cadce5ae8d |
completed | May 3, 2026, 2:26 a.m. |
Created at: May 1, 2026, 12:22 a.m.