Triple
T634397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTSC color television standard |
E15990
|
entity |
| Predicate | luminanceBandwidth |
P1685
|
FINISHED |
| Object | approximately 4.2 MHz |
—
|
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: approximately 4.2 MHz | Statement: [NTSC color television standard, luminanceBandwidth, approximately 4.2 MHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: luminanceBandwidth Context triple: [NTSC color television standard, luminanceBandwidth, approximately 4.2 MHz]
-
A.
designLuminosity
Indicates the specified luminosity level or brightness characteristics that something is designed or intended to have.
-
B.
lightRange
Indicates the distance or area over which a light source effectively emits or illuminates.
-
C.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
D.
spectralResolution
Indicates the fineness with which a system can distinguish or separate different wavelengths or frequencies within a spectrum.
-
E.
memoryBandwidth
Indicates the rate at which data can be transferred to or from a memory system over a given period of time.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ee4ee8481908ad45405e3f3835c |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d0483908190a5ec42a7403c258e |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.