Triple
T13225760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCIR System B |
E314876
|
entity |
| Predicate | visionModulation |
P16366
|
FINISHED |
| Object | negative amplitude modulation |
—
|
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: negative amplitude modulation | Statement: [CCIR System B, visionModulation, negative amplitude modulation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visionModulation Context triple: [CCIR System B, visionModulation, negative amplitude modulation]
-
A.
visionAdaptation
Indicates how an entity’s visual system adjusts or responds to changes in lighting or visual conditions.
-
B.
visionOrSign
Indicates a relationship where something is perceived or presented as a vision, sign, or symbolic manifestation, often conveying a message, omen, or divine indication.
-
C.
vision
Indicates that an entity perceives another entity or object visually, using sight.
-
D.
visualEffect
chosen
Indicates that one entity produces, modifies, or is associated with a particular visual effect on another entity or within a scene.
-
E.
visionOf
Indicates that one entity is a visual representation, image, or depiction of 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3128348190836158467e9cfbe2 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:19 p.m.